How severe is CVE-2014-3490?

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

Which packages are affected by CVE-2014-3490?

CVE-2014-3490 affects the following packages: org.jboss.resteasy:resteasy-client (Maven), org.jboss.resteasy:resteasy-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3490?

Update org.jboss.resteasy:resteasy-client to 2.3.8.SP2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3490 is resolved across your whole dependency graph.

How do I detect CVE-2014-3490 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-2014-3490 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-2014-3490 actively exploited in the wild?

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

CVE-2014-3490 has an EPSS (Exploit Prediction Scoring System) score of 4.6%, placing it in the 92th 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-2014-3490 published, and has it been updated?

CVE-2014-3490 was published on May 14, 2022 and was last updated on December 5, 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-2014-3490 — resteasy-client

Fix: resteasy/Resteasy#521

CVE-2014-3490 is a security 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.

Incorrect Privilege Assignment in RESTEasy

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.jboss.resteasy:resteasy-client☕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 2.3.1 before 2.3.8.SP2 and 3.x before 3.0.9, as used in Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0, does not disable external entities when the resteasy.document.expand.entity.references parameter is set to false, which allows remote attackers to read arbitrary files and have other unspecified impact via unspecified vectors, related to an XML External Entity (XXE) issue. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-0818.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.resteasy:resteasy-client`	≥ 2.3.1&&< 2.3.8.SP2	2.3.8.SP2`org.jboss.resteasy:resteasy-client:2.3.8.SP2`
☕Maven	`org.jboss.resteasy:resteasy-client`	≥ 3.0.0&&< 3.0.9.Final	3.0.9.Final`org.jboss.resteasy:resteasy-client:3.0.9.Final`

Affected Products

2 products · 10 configurations

Application

jboss enterprise application platformredhat

1 version

6.3.0

Application

resteasyredhat

≥ 3.0.0 && ≤ 2.3.7.2

1 version

3.0

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.8.SP2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3490 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 Enterprise Linux 7	`resteasy-base-0:2.3.5-3.el7_0`	RHSA-2014:1011
Red Hat JBoss BPMS 6.0	`resteasy`	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	`resteasy`	RHSA-2015:0235
Red Hat JBoss Data Grid 6.3	see advisory	RHSA-2014:1298
Red Hat JBoss Data Virtualization 6.0	`resteasy`	RHSA-2015:0765
Red Hat JBoss Data Virtualization 6.1	see advisory	RHSA-2015:0675
Red Hat JBoss Enterprise Application Platform 6.3	`resteasy`	RHSA-2014:1039
Red Hat JBoss Enterprise Application Platform 6.3 for RHEL 5	`resteasy-0:2.3.8-5.SP1_redhat_1.1.ep6.el5`	RHSA-2014:1040

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3490 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works