CVE-2014-0449
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 6u71, 7u51, and 8, and Java SE Embedded 7u51, allows remote attackers to affect confidentiality 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 confidenceVulnerability in Oracle Java SE Deployment component (Java Web Start/Plugin) allowing remote attackers to potentially access sensitive information through unspecified vectors. The flaw affects Java SE versions 6u71, 7u51, 8 and Java SE Embedded 7u51.
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= 1.6.0= 1.7.0= 1.8.0= 1.6.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Java versionRun 'java -version' from command line or check Java Control Panel (via Windows Control Panel > Programs > Java) for the version displayed under the General tabAffected if Version displayed is 1.6.0, 1.7.0, or 1.8.0 (corresponds to Java 6, 7, or 8)
-
Confirm Java update version on WindowsOpen Java Control Panel > Advanced > show console output and check the 'Java Runtime Environment Settings' or run 'java -fullversion' to see the full update version numberAffected if Update version is 71 or lower for Java 6, update 51 or lower for Java 7, or any Java 8 version before update 11
-
Verify Java Web Start is configuredCheck for javaws.exe in the Java installation directory (commonly C:\Program Files\Java\jre*\bin\) or locate .jnlp file associations in the systemAffected if Java Web Start (javaws) executable exists and .jnlp file type is associated with Java Web Start
-
Check browser plugin statusExamine installed browser extensions: in Internet Explorer go to Manage Add-ons > Java SE, in Firefox check Add-ons > Plugins for Java Applet Plug-in, in Chrome visit chrome://extensions/Affected if Java Plugin (Java Deployment Toolkit or Java Applet) appears enabled in any web browser
A system is affected if it runs any Java 6 update 71 or earlier, Java 7 update 51 or earlier, or Java 8 (any update before 11) AND has Java Web Start or the Java browser plugin 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 dataUpgrade Java to versions beyond those affected (Java 8 update 11 or later, or latest available). If upgrade is not feasible, disable Java Web Start and the Java browser plugin.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0449 — 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-0449 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