dbcve.org
SatelliteApplication · Redhat

CVE-2016-0363

HIGH · 8.1 CVSS v3.0 Published 2016-06-03
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 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
The com.ibm.CORBA.iiop.ClientDelegate class in IBM SDK, Java Technology Edition 6 before SR16 FP25 (6.0.16.25), 6 R1 before SR8 FP25 (6.1.8.25), 7 before SR9 FP40 (7.0.9.40), 7 R1 before SR3 FP40 (7.1.3.40), and 8 before SR3 (8.0.3.0) uses the invoke method of the java.lang.reflect.Method class in an AccessController doPrivileged block, which allows remote attackers to call setSecurityManager and bypass a sandbox protection mechanism via vectors related to a Proxy object instance implementing the java.lang.reflect.InvocationHandler interface. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-3009.

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 · high confidence

The ClientDelegate class in IBM JDK versions 6, 6R1, 7, 7R1, and 8 contains a flaw where the Method.invoke() is used within an AccessController doPrivileged block without proper safeguards. This allows a malicious Proxy object implementing InvocationHandler to call setSecurityManager, effectively disabling the Java security sandbox and allowing arbitrary code execution.

MitigationUpgrade IBM JDK to versions 6 SR16 FP25+, 6R1 SR8 FP25+, 7 SR9 FP40+, 7R1 SR3 FP40+, or 8 SR3+. If immediate patching is not possible, restrict network exposure of IIOP/CORBA endpoints and disable Java applets in untrusted contexts.

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:= 6.0= 7.0
Enterprise Linux Hpc Node SupplementaryOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server EusOperating system
Affected:= 6.7= 7.2= 7.3= 7.4= 7.5
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.0
Suse Linux Enterprise Software Development KitApplication
Affected:= 11.0= 12.0
Suse Linux Enterprise Module For Legacy SoftwareOperating system
Affected:= 12

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if IBM JDK is installed
    Run 'java -version' and examine the output. IBM JDK typically displays 'IBM Java' in the version string, while Oracle/OpenJDK shows 'Java(TM)' or 'OpenJDK'. Also check for 'java.ibm' package via 'rpm -qa | grep ibmjava' or 'dpkg -l | grep ibmjava' depending on OS.
    Affected if IBM JDK is present (vs Oracle/OpenJDK)
  2. Get the exact IBM JDK version
    Run 'java -version 2>&1' and parse the full version string (e.g., 'JRE 1.8.0_ build...' or 'IBM Java 8.0.x.x'). On RHEL, also check via 'rpm -qa | grep -i ibmjava'. On SLES, use 'rpm -qa | grep -i java' to find ibmjava packages.
    Affected if Version falls within 6.x, 6R1.x, 7.x, 7R1.x, or 8.x before the fixed patch levels (6 SR16 FP25+, 6R1 SR8 FP25+, 7 SR9 FP40+, 7R1 SR3 FP40+, 8 SR3+)
  3. Verify the ClientDelegate class is present
    Locate the IBM JDK installation directory (typically /opt/ibm/java-* or /usr/lib/jvm/ibm*), then find the jre/lib directory. The vulnerable class is in the ORB implementation. Check for presence of 'ClientDelegate.class' within the ibmorb.jar or similar ORB jar files.
    Affected if The IBM JDK ORB implementation containing ClientDelegate.class exists in the JVM installation
  4. Check for exposed IIOP/CORBA endpoints
    Review application server or middleware configuration (such as WebSphere, which uses IBM JDK) for enabled IIOP/CORBA listeners. Check configuration files for 'iiop://' or 'corba://' endpoints. For WebSphere, examine the 'server.xml' and 'iiopEndPoints' settings. Network scan for ports 9100-9109 (typical IIOP range) if applicable.
    Affected if IIOP/CORBA network endpoints are accessible (this is the attack vector for CVE-2016-0363)

User is affected if they are running IBM JDK versions 6, 6R1, 7, 7R1, or 8 (before the fixed patch levels) and have exposed IIOP/CORBA network endpoints accessible to untrusted sources.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IBM JDK to versions 6 SR16 FP25+, 6R1 SR8 FP25+, 7 SR9 FP40+, 7R1 SR3 FP40+, or 8 SR3+. If immediate patching is not possible, restrict network exposure of IIOP/CORBA endpoints and disable Java applets in untrusted contexts.

Fix this in Satellite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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