Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV

CVE-2014-3004 castor

CVE-2014-3004 is a XML External Entity (XXE) vulnerability in org.codehaus.castor:castor. 3 public exploit references exist, so weaponization risk is real. A fix is available for org.codehaus.castor:castor — see the affected versions and patch details below.

Improper Restriction of XML External Entity Reference in Castor

Published
May 13, 2022
Updated
Apr 16, 2026
Affected
2 pkgs
Patched
1 / 2
Exploits
3 known
Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
7.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected
org.codehaus.castor:castorcastor:castor

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

The default configuration for the Xerces SAX Parser in Castor before 1.3.3 allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XML document.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.codehaus.castor:castorall versions1.3.3org.codehaus.castor:castor:1.3.3
Mavencastor:castorall versionsNo fix
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39205remotemultiple✓ Verified

Castor Library - XML External Entity Information Disclosure

by Ron Gutierrez · May 27, 2014

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update org.codehaus.castor:castor to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3004 is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-3004 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

The default configuration for the Xerces SAX Parser in Castor before 1.3.3 allows context-dependent attackers to conduct XML External Entity (XXE) attacks via a crafted XML document.
O3 Security · Impact-Aware SCA

Is CVE-2014-3004 in your dependencies?

O3 Security finds CVE-2014-3004 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2014-3004: castor XXE | O3 Security