ResteasyApplication · Redhat
CVE-2014-7839
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDocumentProvider in RESTEasy 2.3.7 and 3.0.9 does not configure the (1) external-general-entities or (2) external-parameter-entities features, which allows remote attackers to conduct XML external entity (XXE) attacks via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRESTEasy's DocumentProvider fails to disable XML external entity processing by not configuring the external-general-entities and external-parameter-entities features in its XML parser. This allows attackers to inject malicious XML with external entity references to read sensitive files or perform server-side request forgery.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ResteasyApplication
= 2.3.7= 3.0.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RESTEasy versionLocate the resteasy-core jar file in your application classpath or dependencies and check its version metadata (typically in MANIFEST.MF or pom.xml). Common paths include WEB-INF/lib/ or Maven/Gradle dependency declarations.Affected if The installed version is 2.3.7 or 3.0.9
-
Confirm DocumentProvider usageSearch your codebase for imports or references to org.jboss.resteasy.plugins.providers.DocumentProvider, or check if XML marshalling/unmarshalling is performed via RESTEasy's provider framework.Affected if DocumentProvider class is loaded or XML processing through RESTEasy providers is in use
-
Inspect XML parser configuration in DocumentProviderExamine the DocumentProvider source code or its XML parser factory configuration for the presence of XMLConstants.ACCESS_EXTERNAL_DTD and XMLConstants.ACCESS_EXTERNAL_SCHEMA properties, or look for explicit setting of external-general-entities and external-parameter-entities features to false.Affected if The parser configuration does not explicitly disable external-general-entities and external-parameter-entities features (these are not set to false)
You are affected if RESTEasy version 2.3.7 or 3.0.9 is deployed and the DocumentProvider XML parser is used without explicit XXE protection configured in the parser settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataConfigure the DocumentProvider to disable external entity processing by enabling the XXE protection features (external-general-entities and external-parameter-entities set to false) in the XML parser configuration.
Fix this in Resteasy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7839 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-7839 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data