OAuth 2 authorization service vulnerable to DDos attacks
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache CXF | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| JWS 5.7.0 | |||
| cxf-core | cpe:/a:redhat:jboss_enterprise_web_server:5.7 | RHSA-2022:7273 | 2022-11-02T00:00:00Z |
| Red Hat Fuse 7.10 | |||
| cxf-core | cpe:/a:redhat:jboss_fuse:7 | RHSA-2021:5134 | 2021-12-14T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-1003 | 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. |
Github GHSA |
GHSA-7q4h-pj78-j7vg | Authorization service vulnerable to DDos attacks in Apache CFX |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 6.6% (6.593% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.