org.apache.ws.security:wss4j@1.5.10 vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the org.apache.ws.security:wss4j package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Improper Authentication

org.apache.ws.security:wss4j is a project that provides a Java implementation of the primary security standards for Web Services, namely the OASIS Web Services Security (WS-Security) specifications from the OASIS Web Services Security TC.

Affected versions of this package are vulnerable to Improper Authentication. When using TransportBinding, does not properly enforce the SAML SubjectConfirmation method security semantics, which allows remote attackers to conduct spoofing attacks via unspecified vectors.

How to fix Improper Authentication?

Upgrade org.apache.ws.security:wss4j to version 1.6.16, 2.0.2 or higher.

[,1.6.16) [2.0.0,2.0.2)
  • H
Use of a Risky Cryptographic Algorithm

org.apache.ws.security:wss4j is a project that provides a Java implementation of the primary security standards for Web Services, namely the OASIS Web Services Security (WS-Security) specifications from the OASIS Web Services Security TC.

Affected versions of this package are vulnerable to Use of a Risky Cryptographic Algorithm. The PKCS#1 v1.5 Key Transport Algorithm is used to encrypt symmetric keys as part of WS-Security. WSS4J can leak information about where a particular decryption operation fails.

How to fix Use of a Risky Cryptographic Algorithm?

Upgrade org.apache.ws.security:wss4j to version 1.6.4 or higher.

[,1.6.4)
  • M
Access Restriction Bypass

org.apache.ws.security:wss4j 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."

[,1.6.17)