Skip to content
fr Sign in
Not rated

CVE-2021-22696 CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters…

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

Product Affected versions Fixed in
Apache CXF 3.4 earliest → < 3.4.3 3.4.3
Apache CXF 3.3 earliest → < 3.3.10 3.3.10

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache CXF

The 56 CVEs of Apache CXF →
CVE-2026-108039 By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML… Not rated CVE-2026-107938 In Apache CXF, the Netty-based HTTP client transport (cxf-rt-transports-http-netty-client) did not verify that the… Not rated CVE-2026-107937 In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured… Not rated CVE-2026-100227 Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security module Not rated
Track this CVE