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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
11
Affected Products
18
References
apache / cxf
| oracle | business_intelligence | - | - |
| oracle | business_intelligence | - | - |
| oracle | business_intelligence | - | - |
| 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 | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploitability
Impact