CVE-2014-2422
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 · uneditedUnspecified vulnerability in Oracle Java SE 7u51 and 8, and JavaFX 2.2.51, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.
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 confidenceUnspecified vulnerability in Oracle Java SE 7u51/8 and JavaFX 2.2.51 allowing remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to unspecified component.
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= 2.2.51= 1.7.0= 1.8.0= 1.7.0= 1.8.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed JRE/JDK versionRun 'java -version' in command prompt or terminal. On Windows, also check registry under HKLM\SOFTWARE\JavaSoft\Java Runtime Environment for Version value.Affected if Version displays as 1.7.0 (any update before 7u60) or 1.8.0 (any update before 8u40)
-
Check if Java Web Start is enabledOn Windows, verify JWS component exists: look for 'Java Web Start' in Control Panel > Programs, or check for javaws.exe in the Java installation directory (usually under JRE bin folder).Affected if Java Web Start executable exists and is configured to handle JNLP files
-
Verify Java browser plugin statusCheck browser add-on settings: in Internet Explorer go to Manage Add-ons > Java Plug-ins; in Firefox check Plugins page for 'Java Platform SE'; in Chrome navigate to chrome://plugins.Affected if Browser plugin is enabled for any Java version in the affected range
-
Identify JavaFX installation and versionCheck for javafx runtime: locate javafx.properties in the lib folder of JDK/JRE, or search for javafx folder in the Java installation directory. Run 'java -version' also shows JavaFX in some distributions.Affected if JavaFX 2.2.51 is installed as part of the Java installation
-
Confirm Java update mechanismCheck if Java Auto Update is configured: look for 'Java Auto Update' in Windows Services, or check javacpl.exe (Java Control Panel) > Update tab.Affected if System relies on Java Auto Update which may not have applied the April 2014 patch
System is affected if any installed Java JRE/JDK is version 1.7.0 through 7u51, or 1.8.0 through early 8u updates, particularly when Java browser plugin or Java Web Start is enabled.
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 dataApply Oracle Critical Patch Update April 2014 (or later) which addresses this vulnerability, or upgrade to a newer Java 8 release; also restrict Java browser plugins and network exposure to untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2422 — 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-2422 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