CVE-2015-0226

high
Published 2017-10-30 ยท Modified 2025-02-19
CVSS v3
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
7.5

Description

Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

Predictions

Exploit likelihood
83%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 1.6.15-2
sid Fixed 1.6.15-2
forky Fixed 1.6.15-2
bullseye Fixed 1.6.15-2
bookworm Fixed 1.6.15-2

Package impact

EcosystemPackageVulnerableFixed
java Mavenorg.apache.ws.security:wss4j<1.6.171.6.17
java Mavenorg.apache.wss4j:wss4j-ws-security-dom>=2.0.0,<2.0.22.0.2

Application impact

VendorProductVersionsFixed
apache apachewss4j{"endIncluding":"1.6.16"}
apache apachewss4j2.0
apache apachewss4j2.0.0
apache apachewss4j2.0.1

References

CWEs

CWE-327

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.