dbcve.org
Purity\/\/faApplication · Purestorage

CVE-2024-0005

HIGH · 8.8 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to after 6.4.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A condition exists in FlashArray and FlashBlade Purity whereby a malicious user could execute arbitrary commands remotely through a specifically crafted SNMP configuration.

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

This vulnerability in Pure Storage FlashArray and FlashBlade Purity systems allows a remote authenticated attacker to execute arbitrary commands by exploiting a specifically crafted SNMP configuration. The attack leverages the SNMP service to inject commands, likely through maliciously crafted SNMP OIDs or community strings that are not properly validated before execution.

MitigationApply the vendor-supplied patch or firmware update for Purity. If immediate patching is not possible, restrict SNMP access to trusted management networks and disable SNMP if not required. Review SNMP community strings and configuration for any unauthorized changes.

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
Purity\/\/faApplication
Affected:>= 5.0.0, <= 5.0.11>= 5.1.0, <= 5.1.17>= 5.2.0, <= 5.2.7>= 5.3.0, <= 5.3.21>= 6.0.0, <= 6.0.9>= 6.1.0, <= 6.1.25>= 6.2.0, <= 6.2.17>= 6.3.0, <= 6.3.14>= 6.4.0, <= 6.4.10= 6.5.0= 6.6.0
Purity\/\/fbApplication
Affected:>= 3.0.0, <= 3.0.9>= 3.1.0, <= 3.1.5>= 3.2.0, <= 3.2.10>= 3.3.0, <= 3.3.11>= 4.0.0, <= 4.0.6>= 4.1.0, <= 4.1.10>= 4.2.0, <= 4.2.3= 4.3.0= 4.3.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Purity version on FlashArray
    Access the FlashArray web UI and navigate to Storage > Overview, or run `purectl list version` via CLI to retrieve the Purity//fa version
    Affected if Version falls within >= 5.0.0 <= 5.0.11, >= 5.1.0 <= 5.1.17, >= 5.2.0 <= 5.2.7, >= 5.3.0 <= 5.3.21, >= 6.0.0 <= 6.0.9, >= 6.1.0 <= 6.1.25, >= 6.2.0 <= 6.2.17, >= 6.3.0 <= 6.3.14, >= 6.4.0 <= 6.4.10, = 6.5.0, or = 6.6.0
  2. Identify installed Purity version on FlashBlade
    Access the FlashBlade UI and navigate to Settings > Hardware, or run `fbectl get-versions` via CLI to retrieve the Purity//fb version
    Affected if Version falls within >= 3.0.0 <= 3.0.9, >= 3.1.0 <= 3.1.5, >= 3.2.0 <= 3.2.10, >= 3.3.0 <= 3.3.11, >= 4.0.0 <= 4.0.6, >= 4.1.0 <= 4.1.10, >= 4.2.0 <= 4.2.3, = 4.3.0, or = 4.3.1
  3. Determine if SNMP service is enabled
    Check the Purity interface (Settings > SNMP for FlashArray or Settings > Services > SNMP for FlashBlade) or run `pureSNMP get` via CLI to verify if SNMP is configured and active
    Affected if SNMP is enabled and a version within the affected ranges is installed
  4. Review SNMP community string configuration
    Inspect the SNMP community string settings in the Purity interface under SNMP configuration, looking for unexpected or unauthorized community strings
    Affected if Non-standard or unexpected community strings are present in the SNMP configuration

A system is affected if it runs a Purity//fa or Purity//fb version within the specified ranges AND has SNMP service enabled and accessible.

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 a release after 6.4.10
Interim mitigation

Apply the vendor-supplied patch or firmware update for Purity. If immediate patching is not possible, restrict SNMP access to trusted management networks and disable SNMP if not required. Review SNMP community strings and configuration for any unauthorized changes.

Recommended fix Moderate confidence

Upgrade to Purity//fa 5.0.12+, 5.1.18+, 5.2.8+, or 5.3.22+ (preferably latest 5.3.x); Purity//fb 3.0.10+, 3.1.6+, 3.2.11+, or 3.3.12+ (preferably latest 3.3.x)

  1. 1. Identify the current Purity//fa or Purity//fb version running on the affected FlashArray or FlashBlade system
  2. 2. Based on the current version, upgrade to the first version after the affected range: For Purity//fa 5.0.x upgrade to 5.0.12 or later; for 5.1.x upgrade to 5.1.18 or later; for 5.2.x upgrade to 5.2.8 or later; for 5.3.x upgrade to 5.3.22 or later. For Purity//fb 3.0.x upgrade to 3.0.10 or later; for 3.1.x upgrade to 3.1.6 or later; for 3.2.x upgrade to 3.2.11 or later; for 3.3.x upgrade to 3.3.1
  3. 3. Alternatively, upgrade to the latest available Purity//fa 5.3.x or Purity//fb 3.3.x release to ensure all patches are included
  4. 4. Schedule a maintenance window following Pure Storage upgrade procedures
  5. 5. After upgrade, verify the SNMP configuration is functioning correctly and the vulnerability is resolved
  6. 6. Review SNMP access controls to ensure only authorized users can modify SNMP settings
Caveat Review Pure Storage release notes for any functionality changes between versions; test SNMP configurations in non-production environment before upgrading production systems

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

Fix this in Purity\/\/fa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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