CVEvulnerability

CVE-2021-32701

7.5 HIGH Published 2021-06-22 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2021-06-22
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 3.1 ([email protected])
7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0 ([email protected])
4.3 MEDIUM — AV:N/AC:M/Au:N/C:P/I:N/A:N
Weaknesses
CWE-863

Description

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 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.

Affected configurations

• ory oathkeeper 0.38.0 • ory oathkeeper 0.38.1 • ory oathkeeper 0.38.2 • ory oathkeeper 0.38.3 • ory oathkeeper 0.38.4 • ory oathkeeper 0.38.5 • ory oathkeeper 0.38.6 • ory oathkeeper 0.38.7 • ory oathkeeper 0.38.8 • ory oathkeeper 0.38.9 • ory oathkeeper 0.38.10 • ory oathkeeper 0.38.11

Related

Weakness · CWE (1)

  • CWE-863 Incorrect Authorization weakness

References