CVE-2012-0818 — resteasy-client
Fix: resteasy/resteasy@71ace87CVE-2012-0818 is a Information Exposure vulnerability in org.jboss.resteasy:resteasy-client. A fix is available for org.jboss.resteasy:resteasy-client — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy
EPSS Exploitation Probability
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
org.jboss.resteasy:resteasy-clientReal-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
RESTEasy before 2.3.1 allows remote attackers to read arbitrary files via an external entity reference in a DOM document, aka an XML external entity (XXE) injection attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jboss.resteasy:resteasy-client | all versions | 2.3.1org.jboss.resteasy:resteasy-client:2.3.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.resteasy:resteasy-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.resteasy:resteasy-client to 2.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-0818 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2012-0818 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2012-0818. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| JBEWP 5 for RHEL 5 | resteasy-0:1.2.1-10.CP02_patch01.1.ep5.el5 | RHSA-2012:1058 |
| JBoss Enterprise BRMS Platform 5.2 | see advisory | RHSA-2012:0441 |
| Red Hat JBoss BPMS 6.0 | security | RHSA-2014:0371 |
| Red Hat JBoss BRMS 6.0 | security | RHSA-2014:0372 |
| Red Hat JBoss Enterprise Application Platform 5.1 | see advisory | RHSA-2012:1056 |
| Red Hat JBoss Enterprise Application Platform 5 for RHEL 5 | resteasy-0:1.2.1-10.CP02_patch01.1.ep5.el5 | RHSA-2012:1059 |
| Red Hat JBoss Portal 5.2 | see advisory | RHSA-2012:0519 |
| Red Hat JBoss SOA Platform 5.3 | see advisory | RHSA-2012:1125 |
Frequently Asked Questions
Is CVE-2012-0818 in your dependencies?
O3 Security finds CVE-2012-0818 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.