CyberRota Analysis
AI-GeneratedApache CXF's STSTokenValidator and Security Token Service (STS) are vulnerable due to the use of a non-cryptographic 32-bit hash for caching validated security tokens, allowing attackers to exploit hash collisions. This vulnerability could enable an attacker to authenticate as another user without proper validation, potentially leading to unauthorized access and the issuance of STS-signed tokens. Organizations using affected versions of Apache CXF should prioritize upgrading to versions 4.2.4, 4.1.9, or 3.6.13 to mitigate this risk.
Original NVD 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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)