Total vulnerabilities in the database
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.
Software | From | Fixed in |
---|---|---|
apache / cxf | 3.4.0 | 3.4.3 |
apache / cxf | - | 3.3.10 |
oracle / business_intelligence | 12.2.1.3.0 | 12.2.1.3.0.x |
oracle / business_intelligence | 12.2.1.4.0 | 12.2.1.4.0.x |
oracle / business_intelligence | 5.5.0.0.0 | 5.5.0.0.0.x |
oracle / communications_session_route_manager | 8.0.0 | 8.2.4.x |
oracle / communications_session_report_manager | 8.0.0 | 8.2.4.0.x |
oracle / business_intelligence | 5.9.0.0.0 | 5.9.0.0.0.x |
oracle / communications_element_manager | 8.2.2 | 8.2.2.x |
oracle / communications_diameter_intelligence_hub | 8.0.0 | 8.1.0.x |
oracle / communications_diameter_intelligence_hub | 8.2.0 | 8.2.3.x |
![]() |
3.4.0 | 3.4.3 |
![]() |
- | 3.3.10 |
![]() |
3.4.0 | 3.4.3 |
![]() |
- | 3.3.10 |