How severe is CVE-2015-0227?

No CVSS score has been assigned to CVE-2015-0227 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-0227?

CVE-2015-0227 affects the following packages: org.apache.ws.security:wss4j (Maven), org.apache.ws.security:wss4j (Maven), wss4j:wss4j (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-0227?

Update org.apache.ws.security:wss4j to 1.6.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0227 is resolved across your whole dependency graph.

How do I detect CVE-2015-0227 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ws.security:wss4j. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2015-0227 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2015-0227?

O3 pinpoints whether CVE-2015-0227 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2015-0227 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-0227 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2015-0227?

CVE-2015-0227 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-0227 published, and has it been updated?

CVE-2015-0227 was published on February 12, 2015 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2015-0227

CVE-2015-0227 is a CWE-264 vulnerability in org.apache.ws.security:wss4j. O3 Security confirms whether CVE-2015-0227 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Access Control in Apache WSS4J

Also known asGHSA-6r5v-hp32-fjqw

Published

Feb 12, 2015

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕org.apache.ws.security:wss4j☕org.apache.ws.security:wss4j☕wss4j:wss4j

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.ws.security:wss4j`	all versions	1.6.17
☕Maven	`org.apache.ws.security:wss4j`	≥ 2.0.0&&< 2.02	2.02
☕Maven	`wss4j:wss4j`	all versions	1.6.17

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ws.security:wss4j. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.ws.security:wss4j to 1.6.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0227 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2015-0227 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2015-0227. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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."

O3 Security · Impact-Aware SCA

Is CVE-2015-0227 in your dependencies?

O3 detects CVE-2015-0227 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works