JdkApplication · Oracle

CVE-2016-3449

HIGH · 8.3 CVSS v3.0 Published 2016-04-21

Mitigation only

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

See remediation →

90/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Deployment.

Technical summary

dbcve analysis · moderate confidence

An unspecified vulnerability in Oracle Java SE's Deployment component (versions 6u113, 7u99, 8u77) allows remote attackers to affect confidentiality, integrity, and availability. The specific technical exploitation details are not publicly disclosed.

MitigationApply Oracle's Critical Patch Update (CPU) for the affected Java versions, or upgrade to a Java version beyond 8u77 that includes the security fix.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

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

Identify installed Java version

Run 'java -version' from command line or check Java Control Panel > General > About. Note both the major version (1.6, 1.7, 1.8) and update number (e.g., u113).

Affected if The version is Java 6 update 113 or earlier, Java 7 update 99 or earlier, or Java 8 update 77 or earlier.
Determine if Java Deployment component is present

On Windows, check Add/Remove Programs for 'Java SE Development Kit' or 'Java SE Runtime Environment'. On browsers, check if the Java plugin is enabled in browser settings (Chrome: chrome://plugins, Firefox: Add-ons > Plugins).

Affected if Java Runtime Environment or Java plugin is installed and the browser Java plugin is enabled.
Verify Java Deployment toolkit is in use

Check for presence of deployment folder in Java installation directory (e.g., $JAVA_HOME/jre/lib/deploy or C:\Program Files\Java\jre*\lib\deploy). Also check for deployment.properties file in user profile.

Affected if The Deployment component directory exists and contains deployment-related JAR files.
Confirm vulnerability scope

If Java is installed and the version falls within affected ranges (6u113, 7u99, 8u77 or earlier), AND the Deployment component is present/enabled, the environment is potentially affected.

Affected if Java version is at or below 8u77 (for Java 8), at or below 7u99 (for Java 7), or at or below 6u113 (for Java 6), AND the Deployment component is installed.

A user is affected if they have Java 6u113 or earlier, Java 7u99 or earlier, or Java 8u77 or earlier installed WITH the Deployment component present and enabled.

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

Apply Oracle's Critical Patch Update (CPU) for the affected Java versions, or upgrade to a Java version beyond 8u77 that includes the security fix.

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-2016-3449 — 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-2016-3449 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2016-3449?

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 8.3 High

Exploit likelihood EPSS, next 30 days 4.0%

Affects: Jdk

Remediation

A high-priority fix

Fix this in Jdk 9 hrs · Low

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-2016-3449 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