imPC@ndo IT

Tracker / CVE-2021-22696

CVE-2021-22696

High 7.5

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 products and versions

apache cxf · … → 3.3.10
apache cxf · 3.4.0 → 3.4.3
oracle business_intelligence
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
oracle communications_session_report_manager · 8.0.0 → 8.2.4.0
oracle communications_session_route_manager · 8.0.0 → 8.2.4

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References