dbcve.org
SatelliteApplication · Redhat

CVE-2016-0264

MEDIUM · 5.6 CVSS v3.1 Published 2016-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
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
Buffer overflow in the Java Virtual Machine (JVM) 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) allows remote attackers to execute arbitrary code via unspecified vectors.

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

Buffer overflow vulnerability in the IBM JVM (Java Virtual Machine) affecting SDK versions 6, 6R1, 7, 7R1, and 8 before specific patch levels. The flaw allows remote attackers to execute arbitrary code via unspecified vectors.

MitigationUpdate IBM SDK Java to the patched versions: 6 SR16 FP25, 6R1 SR8 FP25, 7 SR9 FP40, 7R1 SR3 FP40, or 8 SR3 or later. Test application functionality after applying the update.

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 Hpc Node SupplementaryOperating system
Affected:= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 5.0= 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:= 5.0= 6.0= 7.0
Linux Enterprise ServerOperating system
Affected:= 11= 10= 12
Linux Enterprise Software Development KitOperating system
Affected:= 11= 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
Low
Integrity
Low
Availability
Low

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

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. Determine if IBM Java SDK is installed
    Run 'java -version' and examine the output for IBM Java or SDK indicators, or check for packages containing 'ibm' in the name using your system package manager (rpm -qa | grep -i ibm or dpkg -l | grep -i ibm)
    Affected if IBM Java SDK or JRE is present on the system
  2. Retrieve the exact IBM Java version
    Run 'java -version 2>&1' to display full version information including Service Refresh (SR) and Fix Pack (FP) levels, or use 'java -XshowSettings:properties -version' to see detailed version properties
    Affected if The version output shows a version before the fixed releases (6 SR16 FP25, 6R1 SR8 FP25, 7 SR9 FP40, 7R1 SR3 FP40, or 8 SR3)
  3. Identify the Java runtime in use
    Check which Java binary is being used by default with 'which java' and 'readlink -f $(which java)', or examine the JAVA_HOME environment variable
    Affected if The default Java points to an IBM JRE/JDK installation
  4. Verify the SDK platform version
    Examine the full version string for SDK 6, 6R1, 7, 7R1, or 8 indicators. On Red Hat systems, query the RPM database with 'rpm -qa | grep -i java' to list installed Java packages
    Affected if The installed version is SDK 6, 6R1, 7, 7R1, or 8 at any SR/FP level below the fixed releases

The environment is affected if IBM Java SDK versions 6 through 8 are installed at any level below 6 SR16 FP25, 6R1 SR8 FP25, 7 SR9 FP40, 7R1 SR3 FP40, or 8 SR3.

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

Update IBM SDK Java to the patched versions: 6 SR16 FP25, 6R1 SR8 FP25, 7 SR9 FP40, 7R1 SR3 FP40, or 8 SR3 or later. Test application functionality after applying the update.

Fix this in Satellite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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