Apache WSS4J

Apache WSS4J: SAML Sender-Vouches Authentication Bypass

Apache WSS4J: WSS4J EncryptedHeader child confusion causing wrong protected-header selection

Apache WSS4J: Streaming WS-SecurityPolicy validation may skip element-protection checks.

Velocity Sandbox Bypass

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.

Apache WSS4J: Insufficient Validation of Derived-Key Parameters

Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference

Apache WSS4J: Unauthenticated denial of service via integer overflow in DER parsing of X.509 certificate extensions

The implementations of PKCS#1 v1.5 key transport mechanism for XMLEncryption in JBossWS and Apache WSS4J before 1.6.5 is susceptible to a Bleichenbacher attack.

Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does not properly enforce the SAML SubjectConfirmation method security semantics, which allows remote attackers to conduct spoofing attacks via unspecified vectors.

Apache WSS4J before 1.6.17 and 2.x before 2.0.2 allows remote attackers to bypass the requireSignedEncryptedDataElements configuration via a vectors related to "wrapping attacks."

Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce