High severity · published Apr 2, 2021
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…
7.5
CVSS
6.6%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)6.6% · higher than 94% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
BI
Business Intelligence · Oracle
5.5.0.0.0; 5.9.0.0.0; 12.2.1.3.0; 12.2.1.4.0 · source: NVD
CD
Communications Diameter Intelligence Hub · Oracle
8.0.0 through 8.1.0; 8.2.0 through 8.2.3 · source: NVD
CS
Communications Session Report Manager · Oracle
8.0.0 through 8.2.4.0 · source: NVD
CS
Communications Session Route Manager · Oracle
8.0.0 through 8.2.4 · source: NVD
CX
Cxf · Apache
before 3.3.10; 3.4.0 before 3.4.3 · source: NVD