dbcve.org
SatelliteApplication · Redhat

CVE-2015-5041

CRITICAL · 9.1 CVSS v3.0 Published 2016-06-06
Fix available
A fix is available. Upgrade to 6.0.16.20 / 6.1.8.20 or later.
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
The J9 JVM in IBM SDK, Java Technology Edition 6 before SR16 FP20, 6 R1 before SR8 FP20, 7 before SR9 FP30, and 7 R1 before SR3 FP30 allows remote attackers to obtain sensitive information or inject data by invoking non-public interface methods.

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 J9 JVM in IBM SDK Java Technology Edition versions 6 before SR16 FP20, 6 R1 before SR8 FP20, 7 before SR9 FP30, and 7 R1 before SR3 FP30 contains a vulnerability that allows remote attackers to bypass Java access controls and invoke non-public interface methods, potentially leading to sensitive information disclosure or arbitrary data injection.

MitigationUpgrade IBM SDK Java to version 6 SR16 FP20 or later, 6 R1 SR8 FP20 or later, 7 SR9 FP30 or later, or 7 R1 SR3 FP30 or later. Alternatively, migrate to an unaffected JVM implementation.

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
Java SdkApplication
Affected:>= 6.0.0.0, < 6.0.16.20>= 6.1.0.0, < 6.1.8.20>= 7.0.0.0, < 7.0.9.30>= 7.1.0.0, < 7.1.3.30
Linux Enterprise ServerOperating system
Affected:= 11= 12
Linux Enterprise Software Development KitOperating system
Affected:= 11= 12
Suse Linux Enterprise ServerOperating system
Affected:= 12
Websphere Application ServerApplication
Affected:<= 3.0.9.20

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
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 IBM Java SDK version
    Run 'java -version' and examine the output for IBM J9 JVM. For detailed version string, use 'java -XshowSettings:all 2>&1 | grep -i version' or check the installation directory for the version manifest file.
    Affected if The version shown is earlier than 6 SR16 FP20, 6 R1 SR8 FP20, 7 SR9 FP30, or 7 R1 SR3 FP30
  2. Check if IBM J9 JVM is the active runtime
    Execute 'which java' and 'java -version' to confirm the J9 JVM is in use. The vulnerability applies specifically to the IBM J9 JVM implementation.
    Affected if The running JVM is IBM J9 and the version is within the affected ranges
  3. Verify WebSphere Application Server version
    Check the WebSphere installation for the IBM Java SDK bundled within. Examine the About WebSphere version information or check the java.exe/javaw.exe version bundled with WebSphere.
    Affected if WebSphere is using an IBM JDK that falls within the affected version ranges
  4. Check Red Hat Satellite version
    Run 'rhn_check --version' or examine /etc/redhat-release and the Satellite server version. Red Hat Satellite 5.6 and 5.7 include the affected IBM Java SDK.
    Affected if Red Hat Satellite version is exactly 5.6 or 5.7
  5. Determine SUSE Linux Enterprise Java runtime
    On SLES 11 or 12, check if IBM Java SDK is installed: 'rpm -qa | grep -i ibm-java' or 'update-alternatives --display java'. The vulnerability applies to IBM Java on these platforms.
    Affected if SLES 11 or 12 is running IBM Java SDK with a version in the affected ranges

You are affected if your environment runs IBM J9 JVM (IBM SDK Java) version 6 before SR16 FP20, 6 R1 before SR8 FP20, 7 before SR9 FP30, or 7 R1 before SR3 FP30, or uses Red Hat Satellite 5.6/5.7, or IBM WebSphere with bundled affected Java versions.

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
Upgrade available Upgrade to 6.0.16.20 / 6.1.8.20 / 7.0.9.30 or later
Fixed in 6.0.16.206.1.8.207.0.9.30
Interim mitigation

Upgrade IBM SDK Java to version 6 SR16 FP20 or later, 6 R1 SR8 FP20 or later, 7 SR9 FP30 or later, or 7 R1 SR3 FP30 or later. Alternatively, migrate to an unaffected JVM implementation.

Recommended fix High confidence

IBM SDK Java Technology Edition 6 SR16 FP20+, 6 R1 SR8 FP20+, 7 SR9 FP30+, or 7 R1 SR3 FP30+

  1. Identify the specific IBM Java SDK version currently installed (e.g., via 'java -version' or checking the installation directory)
  2. For Java 6: Upgrade to IBM SDK Java Technology Edition 6 SR16 FP20 or later
  3. For Java 6 R1: Upgrade to IBM SDK Java Technology Edition 6 R1 SR8 FP20 or later
  4. For Java 7: Upgrade to IBM SDK Java Technology Edition 7 SR9 FP30 or later
  5. For Java 7 R1: Upgrade to IBM SDK Java Technology Edition 7 R1 SR3 FP30 or later
  6. For WebSphere Application Server: Update to version 3.0.9.20+ which contains the fixed Java SDK
  7. For SUSE Linux Enterprise systems: Apply the vendor security updates that include the patched IBM Java packages
  8. Verify the upgrade by running 'java -version' and confirming the new SR/FP level
Caveat IBM Java SDK upgrades may require regression testing of Java applications to ensure compatibility with newer service releases

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

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 the upgrade done

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-2015-5041 — 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-5041 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