CVE-2014-3643
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 · uneditedjersey: XXE via parameter entities not disabled by the jersey SAX parser
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 · moderate confidenceAn XML External Entity (XXE) injection vulnerability in the Jersey framework's SAX parser allows attackers to inject malicious XML via parameter entities that are not disabled, potentially enabling disclosure of internal files, SSRF, or denial of service.
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 dataall versionsCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 if Jersey framework is in useSearch for Jersey JAR files (jersey-*.jar) in the application runtime, or check build configuration (Maven pom.xml or Gradle build.gradle) for jersey-server, jersey-container-*, or other jersey dependenciesAffected if Jersey framework dependencies are present in the application
-
Confirm SAX parser usage via JerseyReview application code to identify if XML parsing is performed using Jersey's XML processing, particularly endpoints that accept XML payloads (e.g., @Consumes(MediaType.APPLICATION_XML) or @XmlRootElement annotated classes)Affected if The application receives or processes XML data through Jersey REST endpoints
-
Check SAX parser configuration for entity settingsInspect the SAXParserFactory or XMLReader configuration used by the application. Look for settings such as setFeature("http://xml.org/sax/features/external-general-entities", false), setFeature("http://xml.org/sax/features/external-parameter-entities", false), or setFeature("http://apache.org/xml/features/disallow-doctype-decl", true)Affected if External entities and parameter entities are enabled, or DTD processing is allowed in the SAX parser configuration
-
Verify XML parser security settings in Jersey contextIf using Jersey's built-in XML support, examine any custom XMLParserConfiguration or XMLReader setups, or check web.xml for custom entity resolver configurations that may disable XXE vectorsAffected if No explicit disabling of external entities, parameter entities, or DTD processing is configured for the SAX parser
The environment is affected if the application uses the Jersey framework to parse XML via its SAX parser and the parser has not been explicitly configured to disable external entities, parameter entities, and DTD processing.
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 Jersey SAX parser to disable external entities, parameter entities, and DTD processing, or upgrade to a Jersey version that has secure XML parser defaults.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3643 — 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-3643 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