How severe is CVE-2012-2379?

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

Which packages are affected by CVE-2012-2379?

CVE-2012-2379 affects the following packages: org.apache.cxf:cxf (Maven), org.apache.cxf:cxf (Maven), org.apache.cxf:cxf (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-2379?

Update org.apache.cxf:cxf to 2.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2379 is resolved across your whole dependency graph.

How do I detect CVE-2012-2379 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-2379 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-2012-2379 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-2379 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-2012-2379?

CVE-2012-2379 has an EPSS (Exploit Prediction Scoring System) score of 4.1%, placing it in the 91th 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.

When was CVE-2012-2379 published, and has it been updated?

CVE-2012-2379 was published on May 13, 2022 and was last updated on November 28, 2024. 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-2012-2379 — cxf

Fix: apache/cxf@440528d

CVE-2012-2379 is a security vulnerability in org.apache.cxf:cxf. A fix is available for org.apache.cxf:cxf — see the affected versions and patch details below.

XML Signature/Encryption Not Validated in Apache CXF

Published

May 13, 2022

Updated

Nov 28, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% 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.cxf:cxf☕org.apache.cxf:cxf☕org.apache.cxf:cxf

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 CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1 or 1.2 policy, does not properly ensure that an XML element is signed or encrypted, which has unspecified impact and attack vectors.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cxf:cxf`	≥ 2.4.0&&< 2.4.8	2.4.8`org.apache.cxf:cxf:2.4.8`
☕Maven	`org.apache.cxf:cxf`	≥ 2.5.0&&< 2.5.4	2.5.4`org.apache.cxf:cxf:2.5.4`
☕Maven	`org.apache.cxf:cxf`	≥ 2.6.0&&< 2.6.1	2.6.1`org.apache.cxf:cxf:2.6.1`

Affected Products

1 product · 13 configurations

Application

cxfapache

13 versions

2.4.02.4.12.4.22.4.32.4.42.4.52.4.62.4.72.5.02.5.12.5.22.5.3

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.cxf:cxf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf to 2.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-2379 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 HatImportant

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0196
JBEWP 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0195
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2012:1559
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2012:1573
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2013:0194
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0192
Red Hat JBoss Enterprise Application Platform 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0191
Red Hat JBoss Enterprise Application Platform 6.0	see advisory	RHSA-2012:1594

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-2379 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works