dbcve.org
SatelliteApplication · Redhat

CVE-2015-1931

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-29
Fix available
A fix is available. Upgrade to 5.0.16.13 / 6.0.16.7 or later.
See remediation →
57/100
Remediation priority · Elevated
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
IBM Java Security Components in IBM SDK, Java Technology Edition 8 before SR1 FP10, 7 R1 before SR3 FP10, 7 before SR9 FP10, 6 R1 before SR8 FP7, 6 before SR16 FP7, and 5.0 before SR16 FP13 stores plaintext information in memory dumps, which allows local users to obtain sensitive information by reading a file.

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

IBM Java Security Components in IBM SDK Java Technology Edition stores plaintext sensitive information (possibly credentials/passwords) in memory dump files. Local users with access to these dump files can read them to obtain the sensitive data in plaintext form.

MitigationUpdate IBM JDK to the fixed versions (Java 8 SR1 FP10+, 7 R1 SR3 FP10+, 7 SR9 FP10+, 6 R1 SR8 FP7+, 6 SR16 FP7+, 5.0 SR16 FP13+) or migrate to a supported Java version. Restrict access to memory dump files.

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.1= 7.2= 7.3= 7.4= 7.5
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0= 7.0
Java SdkApplication
Affected:>= 5.0.0.0, < 5.0.16.13>= 6.0.0.0, < 6.0.16.7>= 6.1.0.0, < 6.1.8.7>= 7.0.0.0, < 7.0.9.10>= 7.1.0.0, < 7.1.3.10>= 8.0.0.0, < 8.0.1.10
Linux Enterprise ServerOperating system
Affected:= 11
Linux Enterprise Software Development KitOperating system
Affected:= 11

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 IBM Java SDK version
    Run 'java -version' or check installed packages (rpm -qa | grep -i ibm-java or dpkg -l | grep -i ibm-java) to determine the exact IBM Java version installed
    Affected if The installed IBM Java version falls within one of the affected ranges: 5.0.0.0 to <5.0.16.13, 6.0.0.0 to <6.0.16.7, 6.1.0.0 to <6.1.8.7, 7.0.0.0 to <7.0.9.10, 7.1.0.0 to <7.1.3.10, or 8.0.0.0 to <8.0.1.10
  2. Locate memory dump files on the system
    Search for common dump file types: heap dumps (.hprof), javacore files (javacore.*.txt), core dumps (core.*), and snap traces (*.snap) in directories such as /var/crash/, /var/tmp/, application working directories, and /tmp/
    Affected if Any memory dump files exist on the system that were generated by IBM Java processes
  3. Verify dump file ownership and permissions
    List dump files with 'ls -la' and check if they are readable by non-privileged users or users other than the application owner
    Affected if Dump files are readable by users other than the application owner or by all users on the system
  4. Check for IBM Java processes with dump-generating configurations
    Inspect running Java processes using 'ps aux | grep java' and review any JVM options that enable dump generation (such as -XX:+HeapDumpOnOutOfMemoryError or -Xdump options)
    Affected if IBM Java processes are running with dump-generating options enabled and those dumps could contain sensitive data

The environment is affected if IBM Java SDK versions within the affected ranges are installed AND memory dump files exist on the system that could be accessed by local users.

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 5.0.16.13 / 6.0.16.7 / 6.1.8.7 or later
Fixed in 5.0.16.136.0.16.76.1.8.7
Interim mitigation

Update IBM JDK to the fixed versions (Java 8 SR1 FP10+, 7 R1 SR3 FP10+, 7 SR9 FP10+, 6 R1 SR8 FP7+, 6 SR16 FP7+, 5.0 SR16 FP13+) or migrate to a supported Java version. Restrict access to memory dump files.

Recommended fix High confidence

IBM Java SDK 5.0 SR16 FP13, 6.0 SR16 FP7, 6.1 SR8 FP7, 7.0 SR9 FP10, 7.1 SR3 FP10, or 8 SR1 FP10 or later

  1. 1. Identify the current IBM Java SDK version installed by running: java -version
  2. 2. For Java 5.0: upgrade to version 5.0.16.13 or later
  3. 3. For Java 6.0: upgrade to version 6.0.16.7 or later
  4. 4. For Java 6.1: upgrade to version 6.1.8.7 or later
  5. 5. For Java 7.0: upgrade to version 7.0.9.10 or later
  6. 6. For Java 7 R1: upgrade to version 7.1.3.10 or later
  7. 7. For Java 8: upgrade to version 8.0.1.10 or later (SR1 FP10)
  8. 8. Download the appropriate IBM Java SDK fix from IBM Fix Central (https://www-945.ibm.com/support/fixcentral/)
Caveat Ensure application compatibility with the new Java version before production deployment; major version upgrades may require code changes

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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