dbcve.org
JdkApplication · Oracle

CVE-2015-4835

HIGH · 10.0 CVSS v2.0 Published 2015-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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, and Java SE Embedded 8u51, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to CORBA, a different vulnerability than CVE-2015-4881.

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

Unspecified vulnerability in Oracle Java SE versions 6u101, 7u85, and 8u60, as well as Java SE Embedded 8u51, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to CORBA (Common Object Request Broker Architecture). The CVSS score of 10 indicates complete network-based exploitation with full impact on all security pillars.

MitigationApply Oracle Java SE security updates to versions beyond 8u60 (or 7u85/6u101). Identify all Java installations across the environment, test application compatibility with the patched version in a staging environment, then deploy the update with rollback capability.

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
JdkApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.6.0= 1.7.0= 1.8.0

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 checks

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

  1. Identify Java installation path and version
    Run 'java -version' or 'java -fullversion' to get the installed Java version. On Windows, also check registry key 'HKLM\SOFTWARE\JavaSoft\Java Runtime Environment' for version information.
    Affected if The version shows 1.6.0_u101 or earlier, 1.7.0_u85 or earlier, or 1.8.0_u60 or earlier (or for Embedded: 1.8.0_u51 or earlier)
  2. Check if CORBA is in use
    Inspect application configuration files (such as application descriptors, .ear/.war files, or naming configuration) for CORBA-related references like 'org.omg.CORBA', 'corbaname', or IIOP endpoints.
    Affected if The application uses CORBA/IIOP remoting, as the vulnerability is specifically in the CORBA implementation
  3. Verify Java deployment configuration
    Check Java Control Panel (Windows) or java/deployment configuration files for CORBA service configurations. Look for 'com.sun.corba.se' related settings in java.security or orb.properties files.
    Affected if CORBA services are enabled or configured in the Java runtime environment
  4. Confirm Java component type
    Determine if the installation is JDK or JRE by checking for 'javac' (JDK) versus only 'java' (JRE), or by examining the installation directory structure.
    Affected if The affected product is either Oracle Jdk or Oracle Jre at the vulnerable versions listed

A user is affected if they have Oracle Java SE (JDK or JRE) versions 1.6.0 up to 6u101, 1.7.0 up to 7u85, or 1.8.0 up to 8u60, and their application or system utilizes CORBA functionality.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Java SE security updates to versions beyond 8u60 (or 7u85/6u101). Identify all Java installations across the environment, test application compatibility with the patched version in a staging environment, then deploy the update with rollback capability.

Recommended fix High confidence

Java 8u361 (or latest available 8.x release)

  1. 1. Identify all systems running affected Java versions (JDK/JRE 1.6.0, 1.7.0, 1.8.0)
  2. 2. Download the latest JDK/JRE 8 from Oracle's official website or your organization's software distribution center
  3. 3. Install the new Java 8 update (8u361 or latest available) on all affected systems
  4. 4. Set JAVA_HOME environment variable to point to the new JDK installation path
  5. 5. Update any application startup scripts or configuration files that reference the old Java path
  6. 6. Verify the new Java version is active by running 'java -version'
  7. 7. Test all Java-based applications to ensure compatibility with the new version
  8. 8. Remove or disable older Java installations after validation
Caveat Applications compiled for older Java versions (e.g., Java 6/7) may encounter compatibility issues; some deprecated APIs may have been removed

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

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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