[
https://issues.apache.org/jira/browse/KNOX-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105239#comment-18105239
]
ASF subversion and git services commented on KNOX-3410:
-------------------------------------------------------
Commit d1c9e0135412dab5e005ceb91d3d88fd0acd561d in knox's branch
refs/heads/v2.1.x from hanicz
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=d1c9e0135 ]
Knox security picks into v2.1.x (#1352)
* KNOX-3188 - Token renewal and revocation should be authorized based on the
group membership of the authenticated subject. (#1083)
(cherry picked from commit 72be9fbd53a9b19483f683025155b665011d7243)
* KNOX-3410: KnoxToken enable/disable endpoints perform no caller autho… (#1343)
* KNOX-3410: KnoxToken enable/disable endpoints perform no caller authorization
* KNOX-3410: Address review comments
(cherry picked from commit f2126008ab764003e9831e48d30302886be93496)
* KNOX-3411: KnoxToken getUserTokens returns every user's token metadat… (#1344)
* KNOX-3411: KnoxToken getUserTokens returns every user's token metadata
without a caller authorization check
* KNOX-3411: Add test clean-up
(cherry picked from commit 049dc0cb894f907efa920a1a2c10fb6ed56fb109)
* KNOX-3416: KnoxSSO redirects to untrusted site (#1346)
* KNOX-3416: KnoxSSO redirects to untrusted site
* KNOX-3416: Clarify error message for userInfo
(cherry picked from commit c3dee56346cfb2670a114d478db0ba2b51aa01f7)
* KNOX-3417: KnoxLdapRealm builds the LDAP search filter from the client
username without RFC-4515 escaping (#1348)
(cherry picked from commit 3cb8ef745c44b39377d855d835198de183a4cef3)
* KNOX-3413: KnoxToken passcode verification accepts a valid passcode for a
different token (#1345)
(cherry picked from commit 5342483a2c7ff229d8819d7df479980753640fc1)
* KNOX-3413: Fix unit test
* KNOX-3418: Path traversal → arbitrary file write/overwrite in the Apache Knox
Admin API (#1349)
(cherry picked from commit de71a60cdf34c842abb8a49f770a0e33fe33c7e9)
* KNOX-3418: Fix jdk17 -> jdk11 compilation fails
---------
Co-authored-by: Sandor Molnar <[email protected]>
> KnoxToken enable/disable endpoints perform no caller authorization
> ------------------------------------------------------------------
>
> Key: KNOX-3410
> URL: https://issues.apache.org/jira/browse/KNOX-3410
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 2.1.0, 3.0.0
> Reporter: Tamás Hanicz
> Assignee: Tamás Hanicz
> Priority: Blocker
> Fix For: 3.0.0, 3.1.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Reported by Andrew Rukin
>
> Apache Knox lets an authenticated user list another user's JWT, API_KEY, and
> CLIENT_ID token records and metadata. The same user can disable or re-enable
> another user's managed tokens by token ID. Knox already enforces ownership
> checks for token revoke. A low-privileged user cannot revoke another user's
> token and receives HTTP 403. The same user can still call disable or enable
> with another user's token ID, receive HTTP 200, and change that token's
> enabled state. I confirmed direct operational impact on official Apache Knox
> 2.1.0. After one low-privileged user disabled another user's managed token,
> the same bearer token immediately stopped working against a JWT-protected
> REST endpoint and returned HTTP 401 "Token ... is disabled".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
