dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0452

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 JAX-WS, a different vulnerability than CVE-2014-0458 and CVE-2014-2423.

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

CVE-2014-0452 is an unspecified vulnerability in Oracle Java SE (versions 6u71, 7u51, 8) and Java SE Embedded 7u51 affecting the JAX-WS (Java API for XML Web Services) component. The vulnerability is remotely exploitable and can impact confidentiality, integrity, and availability, rated HIGH at CVSS 7.5.

MitigationApply the Oracle Critical Patch Update (CPU) for February 2014 or update to a patched Java version beyond the affected releases. For systems unable to update immediately, consider network-level restrictions on JAX-WS endpoints and input validation layers.

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. Verify Java is installed
    Run 'java -version' or 'javac -version' from command line, or check for Java binaries in common paths like /usr/lib/jvm/ on Linux or C:\Program Files\Java\ on Windows
    Affected if No Java installation found means this CVE does not apply
  2. Identify the exact Java version
    Execute 'java -version' (note: output goes to stderr) or use 'java -fullversion' to get the full version string including update number (e.g., 1.7.0_51 or 1.8.0)
    Affected if Version matches 1.6.0, 1.6.0_71, 1.7.0, 1.7.0_51, 1.8.0, or falls within the Java 6 update 71, Java 7 update 51, or Java 8 family releases
  3. Determine if JAX-WS component is in use
    Inspect deployed applications for JAX-WS usage: check application WAR/EAR files for javax.xml.ws.* imports, look for .wsdl files, or review web.xml for servlet mappings to JAX-WS endpoints. Also check if the system processes SOAP-based web service requests
    Affected if JAX-WS is actively processing web service requests or is bundled in deployed applications on the affected Java version
  4. Check Java runtime package information
    On Debian/Ubuntu systems, run 'dpkg -l | grep -i java' or 'apt-cache policy openjdk-*' to see the installed package version. On other systems, check the installation directory for release file containing version details
    Affected if Installed package version corresponds to the affected Ubuntu (10.04, 12.04, 12.10, 13.10, 14.04) or Debian (6.0, 7.0, 8.0) distributions shipping vulnerable Java versions

You are affected if your environment runs Java versions 1.6.0 through 1.6.0_71, 1.7.0 through 1.7.0_51, or Java 8 (1.8.0) and has JAX-WS web services functionality deployed or enabled.

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 Oracle Critical Patch Update (CPU) for February 2014 or update to a patched Java version beyond the affected releases. For systems unable to update immediately, consider network-level restrictions on JAX-WS endpoints and input validation layers.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0452 — 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-0452 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