Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLXF2cDQtcnBtci14d3Jy
Possible bypass of token claim validation when OAuth2 Introspection caching is enabled
Impact
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.
Patches
A patch will be released with v0.38.12-beta.1
.
Workarounds
Per default, caching is disabled for the oauth2_introspection
authenticator. When caching is disabled, this vulnerability does not exist.
Trace
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.
Post-Mortem
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:
- Scope strategy is
none
, cache is enabled, andrequested_scope
is not empty -> cache will not be used; - Scope strategy is
none
, cache is enabled, andrequested_scope
is empty -> cache will be used; - Scope strategy is not
none
, cache is enabled, andrequested_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.
Permalink: https://github.com/advisories/GHSA-qvp4-rpmr-xwrrJSON: https://advisories.ecosyste.ms/api/v1/advisories/MDE2OlNlY3VyaXR5QWR2aXNvcnlHSFNBLXF2cDQtcnBtci14d3Jy
Source: GitHub Advisory Database
Origin: Unspecified
Severity: High
Classification: General
Published: over 3 years ago
Updated: almost 2 years ago
CVSS Score: 7.5
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Identifiers: GHSA-qvp4-rpmr-xwrr
References:
- https://github.com/ory/oathkeeper/security/advisories/GHSA-qvp4-rpmr-xwrr
- https://github.com/advisories/GHSA-qvp4-rpmr-xwrr
Blast Radius: 2.3
Affected Packages
go:github.com/ory/oathkeeper
Dependent packages: 4Dependent repositories: 2
Downloads:
Affected Version Ranges: >= 0.38.0-beta.2, <= 0.38.11-beta.1
Fixed in: 0.38.12-beta.1
All affected versions: 0.38.0-beta.2, 0.38.11-beta.1
All unaffected versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.18, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.11.12, 0.15.0, 0.15.1, 0.15.2, 0.39.0, 0.39.1, 0.39.2, 0.39.3, 0.39.4, 0.40.0, 0.40.1, 0.40.2, 0.40.3, 0.40.4, 0.40.5, 0.40.6, 0.40.7