Incorrect Authorization in ORY Oathkeeper
High severity
GitHub Reviewed
Published
Jun 24, 2021
to the GitHub Advisory Database
•
Updated Feb 1, 2023
Package
Affected versions
>= 0.38.0-beta.2, <= 0.38.11-beta.1
Patched versions
0.38.12-beta.1
Description
Published by the National Vulnerability Database
Jun 22, 2021
Reviewed
Jun 23, 2021
Published to the GitHub Advisory Database
Jun 24, 2021
Last updated
Feb 1, 2023
ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope
foo
using an access token granted with thatfoo
scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scopebar
is made before the cache has expired. Whether the token is granted or not to thebar
scope, introspection will be valid. A patch will be released withv0.38.12-beta.1
. Per default, caching is disabled for theoauth2_introspection
authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked infunc (a *AuthenticatorOAuth2Introspection) Authenticate(...)
. FromtokenFromCache()
it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process.References