CVE intelligence and bounded remediation

CVE-2017-1304 — Ibm Elastic Storage Server security vulnerability

Medium CVSS 6.2

IBM has identified a vulnerability with IBM Spectrum Scale/GPFS utilized on the Elastic Storage Server (ESS)/GPFS Storage Server (GSS) during testing of an unsupported configuration, where users applications are running on an active ESS I/O server node and utilize direct I/O to perform a read or a write to a Spectrum Scale file. This vulnerability may result in the use of an incorrect memory address, leading to a Spectrum Scale/GPFS daemon failure with a Signal 11, and possibly leading to denial of service or undetected data corruption. IBM X-Force ID: 125458.

Severity
Medium
CVSS
6.2 (3.1)
Published
2017-06-21
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-119

Affected products

  • ibm / elastic_storage_server / 2.0.0
  • ibm / elastic_storage_server / 2.5.0
  • ibm / elastic_storage_server / 2.5.5
  • ibm / elastic_storage_server / 3.0.0
  • ibm / elastic_storage_server / 3.0.5
  • ibm / elastic_storage_server / 3.5.0

Showing 6 representative product identities from 13 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.