CVE-2021-22696

CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a "request" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the "request_uri" parameter. CXF was not validating the "request_uri" parameter (apart from ensuring it uses "https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10.
SSRF
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
NISTNIST
7.5 HIGH
NETWORK
LOW
NONE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
apacheCNA
---
---
CVEADP
---
---
Base Score
CVSS 3.x
EPSS Score
Percentile: 64%
VendorProductVersion
apachecxf
𝑥
< 3.3.10
apachecxf
3.4.0 ≤
𝑥
< 3.4.3
oraclebusiness_intelligence
5.5.0.0.0
oraclebusiness_intelligence
5.9.0.0.0
oraclebusiness_intelligence
12.2.1.3.0
oraclebusiness_intelligence
12.2.1.4.0
oraclecommunications_diameter_intelligence_hub
8.0.0 ≤
𝑥
≤ 8.1.0
oraclecommunications_diameter_intelligence_hub
8.2.0 ≤
𝑥
≤ 8.2.3
oraclecommunications_element_manager
8.2.2
oraclecommunications_session_report_manager
8.0.0 ≤
𝑥
≤ 8.2.4.0
oraclecommunications_session_route_manager
8.0.0 ≤
𝑥
≤ 8.2.4
𝑥
= Vulnerable software versions
References