dbcve.org
HadoopApplication · Apache

CVE-2015-7430

HIGH · 8.4 CVSS v3.0 Published 2016-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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 Hadoop connector 1.1.1, 2.4, 2.5, and 2.7.0-0 before 2.7.0-3 for IBM Spectrum Scale and General Parallel File System (GPFS) allows local users to read or write to arbitrary GPFS data 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 · moderate confidence

The Hadoop connector for IBM Spectrum Scale (formerly GPFS) versions 1.1.1, 2.4, 2.5, and 2.7.0-0 through 2.7.0-2 contains a local privilege escalation vulnerability allowing authenticated local users to bypass intended file system access controls and read or write to arbitrary GPFS data files. This is a local access vulnerability with high confidentiality and integrity impact.

MitigationUpgrade the Hadoop connector to version 2.7.0-3 or later. If immediate patching is not feasible, restrict local user access to the GPFS file system and Hadoop connector components, and implement additional filesystem-level access controls to limit exposure.

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
HadoopApplication
Affected:= 1.1.1= 2.4.0= 2.5.0= 2.7.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/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 the GPFS Hadoop connector is installed
    Locate Hadoop connector components for IBM Spectrum Scale (formerly GPFS) - look for connector packages, directories, or binaries named 'gpfs' or 'spectrum scale' within the Hadoop installation
    Affected if The GPFS Hadoop connector is present on the system
  2. Determine the connector version
    Run version detection on the installed Hadoop connector for GPFS - common methods include: connector package manager info, version file in connector directory, or 'hadoop version' with GPFS-specific flags
    Affected if The installed version matches 1.1.1, 2.4.0, 2.5.0, or 2.7.0 through 2.7.0-2
  3. Confirm GPFS file system is in use
    Check if the system mounts or references GPFS (IBM Spectrum Scale) file systems - examine /etc/fstab, mount output, or GPFS-specific commands like mmdf or mmlsfs
    Affected if GPFS file systems are mounted or configured on the same system running the connector
  4. Verify local user access to GPFS data
    Review file permissions and access controls on GPFS-mounted directories - check if unprivileged local users have potential paths to access data files through the connector
    Affected if Local authenticated users exist who could exploit the bypassed access controls
  5. Check for unpatched connector binaries
    Inspect the connector installation directory for library or jar files associated with the affected versions (1.1.1, 2.4, 2.5, 2.7.0-x)
    Affected if Binary files from any of the affected versions are present and in use

You are affected if the GPFS Hadoop connector versions 1.1.1, 2.4.0, 2.5.0, or 2.7.0 through 2.7.0-2 are installed and GPFS file systems are accessible to 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.

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

Upgrade the Hadoop connector to version 2.7.0-3 or later. If immediate patching is not feasible, restrict local user access to the GPFS file system and Hadoop connector components, and implement additional filesystem-level access controls to limit exposure.

Fix this in Hadoop Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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