Apache CXF: STSTokenValidator can accept untrusted SAML assertions because it shares validation state between requests
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.6.13, 4.1.9 and 4.2.4.
In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another's result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while legitimate requests were being processed, and it could be accepted as trusted without ever reaching the STS. Only services that use STSTokenValidator to validate SAML tokens without alwaysValidateToSts set are affected. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | <3.6.13, >=4.0.0 <4.1.9, >=4.2.0 <4.2.4 | 3.6.13, 4.1.9, 4.2.4 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket