First published: Wed Feb 11 2015(Updated: )
Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers to recover the plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/wss4j | <1.6.17 | 1.6.17 |
redhat/wss4j | <2.0.2 | 2.0.2 |
maven/org.apache.wss4j:wss4j-ws-security-dom | >=2.0.0<2.0.2 | 2.0.2 |
maven/org.apache.ws.security:wss4j | <1.6.17 | 1.6.17 |
Apache WSS4J | <=1.6.16 | |
Apache WSS4J | =2.0-beta | |
Apache WSS4J | =2.0.0 | |
Apache WSS4J | =2.0.0-rc1 | |
Apache WSS4J | =2.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-0226 is considered a medium severity vulnerability due to its potential for information leakage.
To fix CVE-2015-0226, upgrade to Apache WSS4J version 1.6.17 or 2.0.2 or later.
CVE-2015-0226 affects Apache WSS4J versions prior to 1.6.17 and 2.0.x versions before 2.0.2.
CVE-2015-0226 is an information disclosure vulnerability related to improper handling of decryption failures.
Remote attackers can exploit CVE-2015-0226 to recover plaintext symmetric keys from systems using affected versions of Apache WSS4J.