Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.ws.security:wss4j Maven |
|
|
| org.apache.wss4j:wss4j-ws-security-dom Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.ws.security:wss4j Maven |
|
|
| org.apache.wss4j:wss4j-ws-security-dom Maven |
|
|
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.
From the CVE record · redhat
Apache WSS4J leaks information about decryption failures when processing encrypted keys or message data. A remote attacker can use a series of crafted messages to make recovery of a symmetric key's plaintext easier; the input does not specify authentication or user-interaction requirements.
Engineers running Maven org.apache.ws.security:wss4j before 1.6.17 or org.apache.wss4j:wss4j-ws-security-dom 2.0.0 through versions before 2.0.2 should check their dependencies.