Skip to content

Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

High severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Jan 25, 2024

Package

maven org.apache.ws.security:wss4j (Maven)

Affected versions

< 1.6.17

Patched versions

1.6.17
maven org.apache.wss4j:wss4j-ws-security-dom (Maven)
>= 2.0.0, < 2.02
2.02

Description

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.

References

Published by the National Vulnerability Database Oct 30, 2017
Published to the GitHub Advisory Database May 14, 2022
Reviewed Jul 6, 2022
Last updated Jan 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2015-0226

GHSA ID

GHSA-vjwc-5hfh-2vv5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.