dbcve.org
Enterprise Linux Desktop SupplementaryOperating system · Redhat

CVE-2014-0418

MEDIUM · 5.1 CVSS v2.0 Published 2014-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 6u65 and 7u45 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Deployment, a different vulnerability than CVE-2013-5889, CVE-2013-5902, CVE-2014-0410, CVE-2014-0415, and CVE-2014-0424.

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

Vulnerability in Oracle Java SE Deployment component (Java Web Start/Java Plug-in) affecting versions 6u65 and 7u45. Allows remote attackers to impact confidentiality, integrity, and availability through unspecified vectors. This is a client-side vulnerability typically exploited via malicious Java Web Start applications or applets loaded from malicious web pages.

MitigationApply Oracle Java SE security patches (later CPU versions superseding 6u65/7u45). Alternatively, disable Java browser plugin and Java Web Start if not required, or employ click-to-play for Java content in browsers.

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
Enterprise Linux Desktop SupplementaryOperating system
Affected:= 5.0= 6.0
Enterprise Linux Hpc Node SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server SupplementaryOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server Supplementary AusOperating system
Affected:= 6.5
Enterprise Linux Server Supplementary EusOperating system
Affected:= 6.5.z
Enterprise Linux Workstation SupplementaryOperating system
Affected:= 6.0
JdkApplication
Affected:= 1.6.0
JreApplication
Affected:= 1.6.0= 1.7.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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/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 installation
    Run 'java -version' or 'javac -version' from command line to determine if Java is installed
    Affected if No Java installation means not affected by this CVE
  2. Identify exact Java version
    Run 'java -version' and note the full version string (e.g., 1.6.0_65 or 1.7.0_45) and compare to the affected versions 6u65 (1.6.0_65) and 7u45 (1.7.0_45)
    Affected if Version matches exactly 6u65 (1.6.0_65) or 7u45 (1.7.0_45) indicates potentially affected
  3. Confirm Java Deployment component presence
    Locate the Java deployment toolkit (javaplugin.jar or deploy.jar) in the JRE lib directory, typically under $JAVA_HOME/lib/ or $JRE_HOME/lib/
    Affected if If deployment JAR files exist and version matches affected releases, the component is present
  4. Check browser plugin status
    In browser, navigate to about:addons (Firefox) or Manage Add-ons (Internet Explorer) to verify if Java Plug-in (Java Deployment Toolkit) is enabled
    Affected if Java browser plugin is enabled and Java version is 6u65 or 7u45 creates exposure to client-side vector

Affected if Java version is exactly 6u65 or 7u45 AND Java Web Start or Java browser plugin is installed and enabled in the environment

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 Oracle Java SE security patches (later CPU versions superseding 6u65/7u45). Alternatively, disable Java browser plugin and Java Web Start if not required, or employ click-to-play for Java content in browsers.

Fix this in Enterprise Linux Desktop Supplementary Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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