First published: Tue Apr 18 2017(Updated: )
An Apache CXF endpoint can be used as an intermediary, where a token credential from the received message is used as a delegation token to obtain a new token from a Security Token Service (STS) for the outbound request. By default, the token retrieved from the STS is cached and associated with the delegation token via an identifier extracted from the delegation token. However, there is a weakness in how the identifier is extracted from the delegation token, which means that an attacker could craft a token which would return an identifer corresponding to a cached token for another user. External References: <a href="http://cxf.apache.org/security-advisories.data/CVE-2017-5656.txt.asc">http://cxf.apache.org/security-advisories.data/CVE-2017-5656.txt.asc</a> Upstream patch: <a href="https://github.com/apache/cxf/commit/66c2c5b99e01a2165a2c5ed9ae34b4b9a512cb39">https://github.com/apache/cxf/commit/66c2c5b99e01a2165a2c5ed9ae34b4b9a512cb39</a>
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/cxf | <3.1.11 | 3.1.11 |
redhat/cxf | <3.0.13 | 3.0.13 |
Apache CXF | >=3.0.0<3.0.13 | |
Apache CXF | >=3.1.0<3.1.11 | |
maven/org.apache.cxf:cxf-core | <=3.0.12 | 3.0.13 |
maven/org.apache.cxf:cxf-core | >=3.1.0<=3.1.10 | 3.1.11 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.