OAuth 2 authorization service vulnerable to DDos attacks
Apache Software Foundation Apache CXF
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf Maven |
|
|
| org.apache.cxf:apache-cxf Maven |
|
Apache Software Foundation Apache CXF
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf Maven |
|
|
| org.apache.cxf:apache-cxf Maven |
|
|
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.
From the CVE record · apache
Apache CXF's JwtRequestCodeFilter did not validate the OAuth 2.0 request_uri parameter beyond requiring HTTPS. When this parameter is used, an attacker can supply a URI that causes the authorization server to fetch a JWT token, exposing it to denial-of-service attacks. The input does not specify whether authentication or user interaction is required.
Engineers running Apache CXF through the Maven packages org.apache.cxf:cxf or org.apache.cxf:apache-cxf should check versions prior to 3.3.10 and versions from 3.4.0 up to, but not including, 3.4.3.