Information Disclosure Vulnerability in WSS4J: Apache WSS4J Prior to 1.6.17

wss4j Updated 02 Oct 2025

Summary

30/10/2017
N/A
Yes i
High
7.5

CVE-2015-0226: 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 plainte... Affects wss4j versions < 1.6.15-2. Fixed in 1.6.15-2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache WSS4J is a widely used library that provides support for web services security, including encryption and signing of messages. It is integral for ensuring the confidentiality and integrity of data exchanged in web services. However, certain versions of WSS4J are vulnerable to an information disclosure issue that can compromise the security of symmetric keys used in encrypted communications.

Vulnerability Detail

The vulnerability, identified as CVE-2015-0226, affects Apache WSS4J versions prior to 1.6.17 and 2.0.x before 2.0.2. It improperly leaks information about decryption failures when decrypting encrypted key or message data. This flaw can be exploited by remote attackers to recover the plaintext form of a symmetric key through a series of crafted messages. The issue arises from an incomplete fix for a previous vulnerability (CVE-2011-2487), highlighting the importance of thorough testing and validation of security patches.

How To Fix

Minimum fixed version

1.6.15-2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wss4j

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate upgrading is not feasible, consider implementing additional security measures such as monitoring for unusual access patterns and employing network-level security controls to limit exposure to potential attackers. However, these are not substitutes for applying the necessary updates.

Conclusion

CVE-2015-0226 is a significant vulnerability in Apache WSS4J that can lead to the exposure of sensitive symmetric keys. It is crucial for users to upgrade to the latest versions to protect their applications from potential exploitation. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your software.

See every vulnerability recorded for wss4j →

Share this vulnerability

FAQ

CVE-2015-0226 is a vulnerability in Apache WSS4J that allows remote attackers to exploit information leakage related to decryption failures, potentially leading to the recovery of symmetric keys.

Versions of Apache WSS4J prior to 1.6.17 and 2.0.x before 2.0.2 are affected by this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using a manifest file like package-lock.json. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The CVSS score for CVE-2015-0226 is 7.5, indicating a high severity level.

If you cannot upgrade right away, implement additional security measures such as monitoring for unusual access patterns and applying network-level security controls to mitigate risks.

Related vulnerabilities

Recent vulnerabilities recorded for wss4j.

How To Fix

Minimum fixed version

1.6.15-2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade wss4j

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback