Apache CXF: Authentication bypass via weak cache keys for validated STS tokens
What fixes it
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
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.
Text from CVE List
Affected versions 3
- Apache CXFaffected: 4.2.0 before 4.2.4CVE List
- Apache CXFaffected: 4.0.0 before 4.1.9CVE List
- Apache CXFaffected: all versions before 3.6.13CVE List