CVE-2014-0448
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 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 confidenceUnspecified vulnerability in Oracle Java SE versions 7u51 and 8 affecting the Deployment component. Remote attackers can achieve complete impact on confidentiality, integrity, and availability through unknown vectors related to Java Web Start or applet deployment mechanisms.
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.7.0= 1.8.0= 1.7.0= 1.8.0>= 4.0.0, < 4.0.0.3>= 8.0.0, < 8.0.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Java versionRun 'java -version' from command line to retrieve the installed Java Runtime Environment versionAffected if Version shows 1.7.0_51 or earlier, or any 1.8.0 version before update 40 (such as 1.8.0_0 through 1.8.0_31)
-
Check Java Development Kit (JDK) versionRun 'javac -version' or check the JDK installation directory for version information if JDK is installedAffected if JDK version matches the same affected ranges as the JRE (1.7.0_51 or earlier, or 1.8.0 before update 40)
-
Identify Java Web Start usageSearch for .jnlp (Java Network Launch Protocol) files on the system and check for javaws.exe process runningAffected if Java Web Start (.jnlp files) is present or was recently used on the system
-
Identify Java applet usageReview browser configurations and check for Java plug-in entries in browsers (such as npapplugin.dll or libnpjp2.so), and look for deployment.config or deployment.properties filesAffected if Java browser plug-in is enabled or deployment configuration files exist indicating applet support is configured
-
Check IBM Forms Viewer version (if applicable)For systems running IBM Forms Viewer, check the product version through its about dialog or version file in the installation directoryAffected if IBM Forms Viewer version is 4.0.0 through 4.0.0.2, or 8.0.0 through 8.0.1.0
A system is affected if it runs Oracle Java SE 7u51 or earlier, or any Java 8 version before update 40, AND has Java Web Start or Java applets enabled or in use.
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 data4.0.0.38.0.1.1
Update Oracle Java SE to a patched version beyond 8u40 that addresses this vulnerability. Prioritize systems running Java applets or Java Web Start applications.
- 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-0448 — 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-0448 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