JdkApplication · Oracle

CVE-2015-0458

HIGH · 7.6 CVSS v2.0 Published 2015-04-16

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

85/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in in Oracle Java SE 6u91, 7u76, and 8u40 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Deployment.

Technical summary

dbcve analysis · moderate confidence

A vulnerability in the Java SE Deployment component (likely Java Web Start or Java Plug-in) allows remote attackers to execute arbitrary code by exploiting unspecified vectors. The vulnerability affects Java versions 6u91, 7u76, and 8u40, impacting all three security properties (confidentiality, integrity, and availability).

MitigationUpdate Java SE to version 8u45 or later (or the latest available version) to obtain the security fix from Oracle's subsequent Critical Patch Updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

Suse Linux Enterprise DesktopOperating system

Affected:= 11.0

OpensuseOperating system

Affected:= 13.2

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed Java version

Run 'java -version' or 'javac -version' from command line, or check JAVA_HOME environment variable and inspect the version file in that directory

Affected if Version output shows 1.6.0 through 1.6.0_91, 1.7.0 through 1.7.0_76, or 1.8.0 through 1.8.0_40 (including 1.6.0, 1.7.0, or 1.8.0 without update numbers)
Verify Java Web Start is present

Check for 'javaws' executable on the system by running 'which javaws' or looking in the Java bin directory under JAVA_HOME

Affected if javaws executable exists and the Java version falls within the affected ranges listed above
Check browser Java plugin status

Inspect browser plugins - in Firefox go to Add-ons > Plugins, or check for npapJavaPlugin.so (Linux) or npDeployJava1.dll (Windows) in browser plugin directories

Affected if Java browser plugin is enabled/installed and the Java version falls within the affected ranges
On Linux, check installed package versions

For SUSE/OpenSUSE: run 'rpm -qa | grep -i jre' or 'zypper se java'. For Debian-based: 'dpkg -l | grep -i openjdk' or 'apt list --installed | grep -i jdk'

Affected if Package version shows 1.6.0, 1.7.0, or 1.8.0 without the fix applied (versions prior to 6u91, 7u76, or 8u40 respectively)

The environment is affected if Java version 1.6.0, 1.7.0, or 1.8.0 is installed AND Java Web Start or the browser Java Plug-in is being used, with the specific vulnerable build numbers being 1.6.0 through 1.6.0_91, 1.7.0 through 1.7.0_76, or 1.8.0 through 1.8.0_40.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update Java SE to version 8u45 or later (or the latest available version) to obtain the security fix from Oracle's subsequent Critical Patch Updates.

Fix this in Jdk Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0458 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-0458?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.6 High

Exploit likelihood EPSS, next 30 days 5.0%

Affects: Jdk

Remediation

A high-priority fix

Fix this in Jdk 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-0458 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References