How severe is CVE-2012-0818?

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

Which packages are affected by CVE-2012-0818?

CVE-2012-0818 affects the following packages: org.jboss.resteasy:resteasy-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-0818?

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.

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

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.

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2012-0818 actively exploited in the wild?

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

CVE-2012-0818 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th 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-2012-0818?

CVE-2012-0818 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2012-0818 was published on May 17, 2022 and was last updated on December 3, 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-0818 — resteasy-client

Fix: resteasy/resteasy@71ace87

CVE-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

Published

May 17, 2022

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.jboss.resteasy:resteasy-client

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.resteasy:resteasy-client`	all versions	2.3.1`org.jboss.resteasy:resteasy-client:2.3.1`

Affected Products

1 product · 13 configurations

Application

resteasyredhat

≤ 2.3.0

12 versions

1.0.01.0.11.0.21.11.22.0.02.0.12.1.02.2.02.2.12.2.22.2.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.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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

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.

O3 Security · Impact-Aware SCA

Is CVE-2012-0818 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works