dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
SatelliteApplication · Redhat

CVE-2015-4902

MEDIUM · 5.3 CVSS v3.1 Published 2015-10-22
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click Patch available

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 · unedited
Unspecified vulnerability in Oracle Java SE 6u101, 7u85, and 8u60 allows remote attackers to affect integrity 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 confidence

Oracle Java SE contains an unspecified vulnerability in the Deployment component affecting versions 6u101, 7u85, and 8u60. The vulnerability allows remote attackers to affect integrity via unknown vectors, likely through malicious applets or web-based Java deployments.

MitigationUpgrade Oracle Java SE to a version beyond the affected releases (6u101, 7u85, 8u60). Oracle Critical Patch Updates address this and similar Deployment component vulnerabilities.

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
SatelliteApplication
Affected:= 5.6= 5.7
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux EusOperating system
Affected:= 6.7= 7.2= 7.3= 7.4= 7.5
Enterprise Linux Eus Compute NodeOperating system
Affected:= 7.2= 7.3
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 5.0_s390x= 6.0_s390x= 7.0_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 6.7_s390x= 7.2_s390x= 7.3_s390x= 7.4_s390x= 7.5_s390x
Enterprise Linux For Power Big EndianOperating system
Affected:= 5.0_ppc= 6.0_ppc64= 7.0_ppc64
Enterprise Linux For Power Big Endian EusOperating system
Affected:= 6.7_ppc64= 7.2_ppc64= 7.3_ppc64= 7.4_ppc64= 7.5_ppc64

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Identify installed Java version
    Run 'java -version' or 'java -fullversion' from command line to obtain the installed Java SE version
    Affected if Version displays as 6u101, 7u85, or 8u60
  2. Check Java deployment toolkit status
    Inspect Java Control Panel or check for 'deployment.properties' file typically located in $JAVA_HOME/lib/deploy/ or user home directory under .java/deployment/
    Affected if Deployment component is present and enabled on a vulnerable Java version
  3. Verify Java installation path
    Use 'which java' or 'echo $JAVA_HOME' to locate the Java installation directory, then check the 'release' file for exact version string
    Affected if The release file contains version strings matching 1.6.0_101, 1.7.0_85, or 1.8.0_60
  4. Check for Java Web Start usage
    Look for .jnlp files or Java Web Start launcher (javaws) on the system, as the Deployment component handles Java Web Start
    Affected if Java Web Start is configured and the underlying Java version is 6u101, 7u85, or 8u60

You are affected if any installed Java runtime is version 6u101, 7u85, or 8u60 and the Java Deployment component (Java Web Start or Java Plugin) is enabled or in use.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Upgrade Oracle Java SE to a version beyond the affected releases (6u101, 7u85, 8u60). Oracle Critical Patch Updates address this and similar Deployment component vulnerabilities.

Recommended fix Moderate confidence

Java 6u105 or later (for Java 6 deployments); Java 7u91 or later (for Java 7 deployments); Java 8u77 or later (for Java 8 deployments)

  1. Identify the installed Java package using: rpm -qa | grep -i java or java -version
  2. For RHEL 5.x systems: Run 'yum update java-1.6.0-ibm' or 'yum update java-1.7.0-ibm' depending on the installed version
  3. For RHEL 6.x and 7.x systems: Run 'yum update java-1.7.0-openjdk' or 'yum update java-1.8.0-openjdk' depending on the installed version
  4. Alternatively, for Oracle Java SE, download and install the fixed versions: Java 6u105+, Java 7u91+, or Java 8u77+ from Oracle's official JDK downloads
  5. After update, verify the fixed version using: java -version
  6. Restart any running Java applications to ensure they use the updated runtime
Caveat Ensure compatibility of applications with the newer Java version before deploying in production environments; some legacy applications may require code changes for newer Java versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Satellite Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4902 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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