GHSA-qvp4-rpmr-xwrrHigh· 7.5▾ TwilightPossible bypass of token claim validation when OAuth2 Introspection caching is enabled
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
When you make a request to an endpoint that requires the scope foo using an access token granted with that foo scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope bar is made before the cache has expired. Whether the token is granted or not to the bar scope, introspection will be valid.
A patch will be released with v0.38.12-beta.1.
Per default, caching is disabled for the oauth2_introspection authenticator. When caching is disabled, this vulnerability does not exist.
The cache is checked in func (a *AuthenticatorOAuth2Introspection) Authenticate(...). From tokenFromCache() 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.
To avoid this from happening again we enabled codecov with a strict policy on the Ory Oathkeeper repository: Without an increase in code coverage the PR can not be merged.
To address this issue and any regressions we have added a test suite ensuring that the cache behaviour is correct in the different scenarios:
none, cache is enabled, and requested_scope is not empty -> cache will not be used;none, cache is enabled, and requested_scope is empty -> cache will be used;none, cache is enabled, and requested_scope is not empty -> cache will be used;as well as validating if iss, aud, exp, token_use, and scope are validated.
Additionally, we added CodeQL scanning to the CI.
github.com/ory/oathkeeper >= 0.38.0-beta.2, < 0.38.12-beta.1Upgrade to a patched release:
github.com/ory/oathkeeper 0.38.12-beta.1Connected by shared product, vendor, weakness, or advisory.
GO-2022-0920NoneIncorrect Authorization in ORY Oathkeeper in github.com/ory/oathkeeper
GHSA-vfvf-6gx5-mqv6High· 7.5Incorrect Authorization in ORY Oathkeeper
CVE-2020-15223High· 8.0Ory fosite contains Improper Handling of Exceptional Conditions
CVE-2020-15222High· 8.1Token reuse in Ory fosite
CVE-2020-15233Medium· 6.1OAuth2 Redirect URL validity does not respect query parameters and character casing for loopback addresses
CVE-2020-5300Medium· 5.8Authentication Bypass in hydra