CVE-2021-22696
No exploitation reported by the sources we read.
- Published2021-04-02
- WeaknessCWE-400 · CWE-918
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2021-04-0210:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-22696?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-22696?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.5 | = 5.5.0.0.0 | no fix published | NVD |
| 5.9 | = 5.9.0.0.0 | no fix published | NVD |
| 12.2 | = 12.2.1.3.0 | no fix published | NVD |
| 12.2 | = 12.2.1.4.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.4 | ≥ 3.4.0, < 3.4.3 | 3.4.3 | NVD · OSV |
| 3.3 | < 3.3.10 | 3.3.10 | NVD · OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.x | ≥ 8.0.0, ≤ 8.1.0 | no fix published | NVD |
| 8.2 | ≥ 8.2.0, ≤ 8.2.3 | no fix published | NVD |
3 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- cxf.apache.orgVendor Advisory
- www.oracle.comPatch
- www.oracle.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2021-04-02
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-22696?
Is CVE-2021-22696 actively exploited?
What is the CVSS score for CVE-2021-22696?
Running cxf? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.