CVE-2015-0226: Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

CVE-2015-0226 · Severity: low · CVSS 3.1 · Published 2022-05-14

Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

Technologies: org.apache.ws.security:wss4j (Maven). Vendors: Maven.

Quick answers

Is CVE-2015-0226 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-0226 being exploited in the wild.
How severe is CVE-2015-0226?
Low severity, with a CVSS score of 3.1, published 14 May 2022.
Which products and versions are affected?
org.apache.ws.security:wss4j (Maven) ECOSYSTEM:introduced=0,fixed=1.6.17; org.apache.wss4j:wss4j-ws-security-dom (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.2.
Is there a fix for CVE-2015-0226?
Yes. org.apache.ws.security:wss4j (Maven): upgrade to 1.6.17 or later; org.apache.wss4j:wss4j-ws-security-dom (Maven): upgrade to 2.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-0226?
Check whether you run org.apache.ws.security:wss4j (Maven) or org.apache.wss4j:wss4j-ws-security-dom (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.ws.security:wss4j (Maven): upgrade to 1.6.17 or later
    # set org.apache.ws.security:wss4j to 1.6.17 in your pom.xml or build.gradle
  • org.apache.wss4j:wss4j-ws-security-dom (Maven): upgrade to 2.0.2 or later
    # set org.apache.wss4j:wss4j-ws-security-dom to 2.0.2 in your pom.xml or build.gradle

Affected products

  • org.apache.ws.security:wss4j (Maven) ECOSYSTEM:introduced=0,fixed=1.6.17
  • org.apache.wss4j:wss4j-ws-security-dom (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.2

Identifiers

  • CVE-2015-0226
  • GHSA-vjwc-5hfh-2vv5

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.