Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2021-32701— Possible bypass of token claim validation when OAuth2 Introspection caching is enabled

Quick assessment

Affected
ory oathkeeper
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

ORY Oathkeeper是开源的一个身份访问代理(IAP)和访问控制决策API，基于一组访问规则授权HTTP请求。 ORY Oathkeeper存在安全漏洞，该漏洞源于一个身份访问代理(IAP)和访问控制决策API，基于一组访问规则授权HTTP请求。

CVSS 7.5 · High EPSS 1.63% · P75
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2021-32701

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Possible bypass of token claim validation when OAuth2 Introspection caching is enabled
Source: CVE Program / CVE List V5
Vulnerability 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(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5
Vulnerability Title
ORY Oathkeeper 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
ORY Oathkeeper是开源的一个身份访问代理(IAP)和访问控制决策API，基于一组访问规则授权HTTP请求。 ORY Oathkeeper存在安全漏洞，该漏洞源于一个身份访问代理(IAP)和访问控制决策API，基于一组访问规则授权HTTP请求。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
ory oathkeeper >=v0.38.0-beta.2, < v0.38.12-beta.1 -

II. Public POCs for CVE-2021-32701

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2021-32701

请登录查看更多情报信息。

Patches & Fixes for CVE-2021-32701 (2)

Vendor Advisories for CVE-2021-32701 (1)

IV. Related Vulnerabilities

Same product: oathkeeper
Same vendor: ory
Same weakness: CWE-863

V. Comments for CVE-2021-32701

No comments yet

Leave a comment