dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-2414

HIGH · 7.5 CVSS v2.0 Published 2014-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in Oracle Java SE 6u71, 7u51, and 8, and Java SE Embedded 7u51, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JAXB.

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 confidence

A remote code execution vulnerability in Oracle Java SE related to JAXB (Java Architecture for XML Binding) processing of untrusted XML data. The unspecified vulnerability allows attackers to impact confidentiality, integrity, and availability through malicious XML parsing, likely involving XML External Entity (XXE) injection or unsafe deserialization within the JAXB component.

MitigationApply the relevant Oracle Java SE critical patch update (CPU) for April 2014 which addresses this vulnerability in affected versions (6u71, 7u51, 8, and Java SE Embedded 7u51). If immediate patching is not possible, consider disabling or restricting JAXB processing for untrusted XML sources.

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
Ubuntu LinuxOperating system
Affected:= 10.04= 12.04= 12.10= 13.10= 14.04
Debian LinuxOperating system
Affected:= 6.0= 7.0= 8.0
JdkApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.6.0= 1.7.0= 1.8.0

CVSS 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
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java version
    Run 'java -version' or 'javac -version' to get the full version string. On Linux systems, also check /usr/lib/jvm/ for installed JDK/JRE directories.
    Affected if The version shows 1.6.0, 1.7.0, or 1.8.0 (any update version within these major releases)
  2. Confirm Java/JDK/JRE package installation on Debian-based Linux
    On Ubuntu, run 'dpkg -l | grep -i java' or 'dpkg -l | grep -i jdk'. On Debian, use the same commands to list installed Java packages.
    Affected if Installed packages are from the affected version ranges (1.6.0, 1.7.0, 1.8.0)
  3. Identify JAXB library presence
    Search for jaxb-api.jar, jaxb-impl.jar, or jaxb-core.jar in the Java installation directory (typically under JAVA_HOME/lib or JRE_HOME/lib) or within application WEB-INF/lib or classpath.
    Affected if JAXB libraries are present in the Java runtime or application classpath
  4. Determine if application processes untrusted XML
    Review application configuration and code for XML parsing usage, particularly where external/untrusted XML sources are processed. Check for javax.xml.bind, JAXB unmarshaller, or XMLReader usage in application logs or configuration.
    Affected if The application uses JAXB to parse XML from untrusted network sources or user-provided data
  5. Check for application exposure to network XML input
    Audit application endpoints, services, or configurations that accept XML input from external sources, including SOAP web services, REST endpoints with XML content types, or file upload features that process XML.
    Affected if Network-accessible endpoints accept and process XML data without validation

You are affected if you run any Java 1.6.0, 1.7.0, or 1.8.0 installation that uses JAXB to process XML from untrusted sources and the April 2014 CPU has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Oracle Java SE critical patch update (CPU) for April 2014 which addresses this vulnerability in affected versions (6u71, 7u51, 8, and Java SE Embedded 7u51). If immediate patching is not possible, consider disabling or restricting JAXB processing for untrusted XML sources.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2414 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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