CVEvulnerability

CVE-2021-22696

7.5 HIGH Published 2021-04-02 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2021-04-02
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:N/I:N/A:H
CVSS 2.0 ([email protected])
5.0 MEDIUM — AV:N/AC:L/Au:N/C:N/I:N/A:P
Weaknesses
CWE-400, CWE-918

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.

Affected configurations

• apache cxf (< 3.3.10) • apache cxf (>= 3.4.0 < 3.4.3) • oracle business intelligence 5.5.0.0.0 • oracle business intelligence 5.9.0.0.0 • oracle business intelligence 12.2.1.3.0 • oracle business intelligence 12.2.1.4.0 • oracle communications diameter intelligence hub (>= 8.0.0 <= 8.1.0) • oracle communications diameter intelligence hub (>= 8.2.0 <= 8.2.3) • oracle communications element manager 8.2.2 • oracle communications session report manager (>= 8.0.0 <= 8.2.4.0) • oracle communications session route manager (>= 8.0.0 <= 8.2.4)

Related

Weakness · CWE (2)

  • CWE-400 Uncontrolled Resource Consumption weakness
  • CWE-918 Server-Side Request Forgery weakness

References