dbcve.org
Purity\/\/faApplication · Purestorage

CVE-2024-0004

HIGH · 7.2 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to after 6.4.10 or later.
See remediation →
78/100
Remediation priority · High
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 Purity whereby an user with array admin role can execute arbitrary commands remotely to escalate privilege on the array.

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

FlashArray Purity contains a privilege escalation vulnerability where an authenticated user with array admin role can execute arbitrary commands remotely. This allows the attacker to escalate beyond their intended administrative privileges to gain full control of the array.

MitigationRestrict or eliminate the ability for array admin users to execute arbitrary system commands. Implement proper command sandboxing or role-based access controls to prevent privilege escalation from the array admin role.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/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
    Access the FlashArray management interface or run the command `purectl list version` or check via the web UI under Settings > Overview to retrieve the Purity firmware version.
    Affected if The installed version falls within any of these ranges: 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, or is exactly 6.5.0.
  2. Review array admin user accounts
    In the FlashArray UI, navigate to Settings > Users or run `pureadmin list` to enumerate all users assigned the array admin role.
    Affected if There exists any user account with the array admin role currently active on the system.
  3. Verify remote API access is enabled
    Check the FlashArray network settings to confirm whether the REST API or SSH interface is accessible from network segments where non-administrative users operate.
    Affected if Remote API or SSH access is permitted for array admin users from any network location.
  4. Inspect audit logs for command execution
    Review the FlashArray audit logs under Settings > Audit or run `pureaudit` to look for entries indicating arbitrary command execution, shell access, or API calls that invoke system commands.
    Affected if Audit logs contain records of arbitrary system commands being executed by users with array admin privileges.

Your environment is affected if the installed Purity version matches any of the affected version ranges AND there are array admin users configured with the ability to execute commands remotely.

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

Restrict or eliminate the ability for array admin users to execute arbitrary system commands. Implement proper command sandboxing or role-based access controls to prevent privilege escalation from the array admin role.

Recommended fix Moderate confidence

Purity//FA 5.3.22 or later (or respective fix in 5.0.12+, 5.1.18+, 5.2.8+ branches)

  1. Identify the currently installed Purity//FA version using the Pure Storage management interface or CLI
  2. Determine which version branch (5.0.x, 5.1.x, 5.2.x, or 5.3.x) is currently in use
  3. Upgrade to the next available version in the respective branch that addresses the vulnerability
  4. Verify the upgrade by checking the Purity version post-upgrade
  5. Confirm that the array admin role permissions have been properly scoped after upgrade
Caveat Review Pure Storage release notes for any changes to admin role permissions or API behavior in the target version

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

Fix this in Purity\/\/fa Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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