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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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 is the EPSS score for CVE-2015-0227?

CVE-2015-0227 has an EPSS (Exploit Prediction Scoring System) score of 7.5%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

CVE-2015-0227 — wss4j

CVE-2015-0227 is a CWE-264 vulnerability in org.apache.ws.security:wss4j. A fix is available for org.apache.ws.security:wss4j — see the affected versions and patch details below.

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

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`org.apache.ws.security:wss4j:1.6.17`
☕Maven	`org.apache.ws.security:wss4j`	≥ 2.0.0&&< 2.02	2.02`org.apache.ws.security:wss4j:2.02`
☕Maven	`wss4j:wss4j`	all versions	1.6.17`wss4j:wss4j:1.6.17`

Affected Products

1 product · 4 configurations

Application

wss4japache

≤ 1.6.16

2 versions

2.0.02.0.1

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss A-MQ 6.2	see advisory	RHSA-2015:1177
Red Hat JBoss Data Grid 6.4	`wss4j`	RHSA-2015:0773
Red Hat JBoss Enterprise Application Platform 6.4	see advisory	RHSA-2015:0849
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5	`apache-commons-cli-eap6-0:1.2.0-1.redhat_8.1.ep6.el5`	RHSA-2015:0846
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6	`apache-commons-cli-eap6-0:1.2.0-1.redhat_8.1.ep6.el6`	RHSA-2015:0847
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7	`apache-commons-daemon-eap6-1:1.0.15-8.redhat_1.ep6.el7`	RHSA-2015:0848
Red Hat JBoss Fuse 6.2	see advisory	RHSA-2015:1176
Red Hat JBoss Portal 6.2	see advisory	RHSA-2015:1009

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?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works