Apache Software Foundation Apache CXF
Apache CXF: Authentication bypass via weak cache keys for validated STS tokens
Apache CXF's STSTokenValidator and Security Token Service (STS) cached validated security tokens under a non-cryptographic 32-bit hash of the token (Java Arrays.hashCode/hashCode()), and treated a cache hit as proof that the presented token had already been validated. An attacker could craft a token (for example a UsernameToken or a self-signed SAML Assertion) whose hash collides with a cached entry. The token would then be accepted without password validation, signature trust verification or a call to the STS. This could let the attacker authenticate as another user and, through STS token validation or renewal, obtain STS-signed tokens for that identity. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.2.0, < 4.2.4
- >= 4.0.0, < 4.1.9
- < 3.6.13
Fixed in 4.2.4, 4.1.9, 3.6.13
Mitigation
Upgrade Apache CXF to 4.2.4 or 4.1.9 or 3.6.13 or later.
References
- Vendor advisory lists.apache.org/thread.html/qthbnsyhqsxhl9p2h9v5dg4…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.