dbcve.org
JdkApplication · Oracle

CVE-2014-2428

HIGH · 7.6 CVSS v2.0 Published 2014-04-16
Fix available
A fix is available. Upgrade to 4.0.0.3 / 8.0.1.1 or later.
See remediation →
85/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 unknown vectors related to Deployment.

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

Oracle Java SE vulnerability in the Deployment component affecting versions 6u71, 7u51, 8, and Java SE Embedded 7u51. Allows remote attackers to achieve complete impact on confidentiality, integrity, and availability through unknown vectors, likely via malicious applets or Java Web Start files.

MitigationApply Oracle Java Critical Patch Updates to versions beyond 8u5 (or 7u55/6u71 depending on baseline). If patching is not feasible, disable Java browser plugins and Java Web Start through Java Control Panel or group policy.

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
JdkApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
Forms ViewerApplication
Affected:>= 4.0.0, < 4.0.0.3>= 8.0.0, < 8.0.1.1

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:H/Au:N/C:C/I:C/A:C

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' from command line, or check Java Control Panel > General > About. For JDK, also check 'javac -version'. Record the full version string (e.g., 1.7.0_51).
    Affected if Version is 1.6.0_u71, 1.7.0_51, 1.8.0 (any update), or 1.7.0_51 for Java SE Embedded
  2. Verify Java Runtime Environment is installed
    On Windows, check for JRE installation in C:\Program Files\Java\ or via 'java -verbose' command. On Linux, check /usr/lib/jvm/ or run 'which java'.
    Affected if Java JRE or JDK is installed with a version matching the affected range in step 1
  3. Confirm Java Web Start is enabled
    Open Java Control Panel > General > Security, or check for javaws.exe in the Java installation directory and verify it is not blocked via deployment.properties file in Java deployment config directory.
    Affected if Java Web Start (javaws) is available and not explicitly disabled; this is the primary attack vector for this CVE
  4. Check Java browser plugin status
    On Windows, check browser add-on settings (Internet Explorer: Manage Add-ons) for 'Java Plug-in' or 'NextGeneration Java Plug-in'. On Firefox, check Add-ons > Plugins. On Chrome, check chrome://plugins.
    Affected if Java browser plugin is enabled in any web browser; this is an attack vector for malicious applets
  5. Identify IBM Forms Viewer installation and version
    If Oracle Java is bundled with IBM Forms Viewer, check the IBM Forms installation directory for version.info or ibmforms.cfg files. Run 'java -version' from the IBM Forms bin directory if available.
    Affected if IBM Forms Viewer version is 4.0.0 through 4.0.0.2, or 8.0.0 through 8.0.1.0

You are affected if Java (JDK/JRE) version 1.6.0_u71, 1.7.0_51, 1.8.0, or Java SE Embedded 7u51 is installed AND Java Web Start or browser plugins are enabled, or if IBM Forms Viewer version falls within the stated vulnerable ranges.

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
Upgrade available Upgrade to 4.0.0.3 / 8.0.1.1 or later
Fixed in 4.0.0.38.0.1.1
Interim mitigation

Apply Oracle Java Critical Patch Updates to versions beyond 8u5 (or 7u55/6u71 depending on baseline). If patching is not feasible, disable Java browser plugins and Java Web Start through Java Control Panel or group policy.

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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