CVE-2021-22696
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.
How to fix
- apache cxf3.3.10, 3.4.3 or later
- org.apache.cxf:cxf3.4.3, 3.3.10 or later
- org.apache.cxf:apache-cxf3.4.3, 3.3.10 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache cxf | v < 3.3.10, 3.4.0 ≤ v < 3.4.3 | 3.3.10, 3.4.3 |
| oracle business_intelligence | 5.5.0.0.0, 5.9.0.0.0, 12.2.1.3.0, 12.2.1.4.0 | — |
| oracle communications_diameter_intelligence_hub | 8.0.0 ≤ v ≤ 8.1.0, 8.2.0 ≤ v ≤ 8.2.3 | — |
| oracle communications_element_manager | 8.2.2 | — |
| oracle communications_session_report_manager | 8.0.0 ≤ v ≤ 8.2.4.0 | — |
| oracle communications_session_route_manager | 8.0.0 ≤ v ≤ 8.2.4 | — |
| org.apache.cxf:cxfMaven | 3.4.0 ≤ v < 3.4.3, v < 3.3.10 | 3.4.3, 3.3.10 |
| org.apache.cxf:apache-cxfMaven | 3.4.0 ≤ v < 3.4.3, v < 3.3.10 | 3.4.3, 3.3.10 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.