dbcve.org
Storwize V7000 FirmwareOperating system · Ibm

CVE-2018-1463

MEDIUM · 6.5 CVSS v3.1 Published 2018-05-17
Fix available
A fix is available. Upgrade to 7.5.0.14 / 7.7.1.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 SAN Volume Controller, IBM Storwize, IBM Spectrum Virtualize and IBM FlashSystem products ( 6.1, 6.2, 6.3, 6.4, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.6.1, 7.7, 7.7.1, 7.8, 7.8.1, 8.1, and 8.1.1) could allow an authenticated user to access system files they should not have access to some of which could contain account credentials. IBM X-Force ID: 140368.

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 SAN Volume Controller, Storwize, Spectrum Virtualize, and FlashSystem products contain an improper access control vulnerability allowing authenticated users to access system files outside their authorized scope, including files potentially containing account credentials.

MitigationApply IBM security patches for this vulnerability (contact IBM support for specific fix packages). Restrict user access permissions to system files and review role-based access controls until patches can be applied.

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
Storwize V7000 FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Storwize V5000 FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Storwize V3700 FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Storwize V3500 FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Storwize V9000 FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
San Volume Controller FirmwareOperating system
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Spectrum VirtualizeApplication
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1
Spectrum Virtualize For Public CloudApplication
Affected:>= 6.1.0.0, < 7.5.0.14>= 7.7.0.0, < 7.7.1.9>= 7.8.0.0, < 7.8.1.6>= 8.1.1.0, < 8.1.1.2>= 8.1.2.0, < 8.1.2.1

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

CVSS:3.1/AV:N/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 the product model
    Log into the system management GUI or CLI and determine if the device is one of: Storwize V7000, V5000, V3700, V3500, V9000, SAN Volume Controller, Spectrum Virtualize, or Spectrum Virtualize for Public Cloud
    Affected if The product model matches any of the affected product families listed in the CVE
  2. Retrieve the installed firmware version
    Access the system management interface and locate the firmware or software version information, typically found in the GUI under System > Settings > Version or via CLI command such as lsversion
    Affected if Unable to retrieve a firmware version for comparison
  3. Compare version against affected ranges
    Check if the installed version falls within any of these vulnerable ranges: 6.1.0.0 to 7.5.0.13, 7.7.0.0 to 7.7.1.8, 7.8.0.0 to 7.8.1.5, 8.1.1.0 to 8.1.1.1, or 8.1.2.0 to 8.1.2.0
    Affected if The installed version is within any of the affected version ranges listed above

A user is affected if they are running any of the listed IBM storage products with a firmware version that falls within the specified vulnerable ranges.

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
Upgrade available Upgrade to 7.5.0.14 / 7.7.1.9 / 7.8.1.6 or later
Fixed in 7.5.0.147.7.1.97.8.1.6
Interim mitigation

Apply IBM security patches for this vulnerability (contact IBM support for specific fix packages). Restrict user access permissions to system files and review role-based access controls until patches can be applied.

Fix this in Storwize V7000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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