dbcve.org
Purity\/\/faApplication · Purestorage

CVE-2022-32554

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to 3.1.13 / 3.2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Pure Storage FlashArray products running Purity//FA 6.2.0 - 6.2.3, 6.1.0 - 6.1.12, 6.0.0 - 6.0.8, 5.3.0 - 5.3.17, 5.2.x and prior Purity//FA releases, and Pure Storage FlashBlade products running Purity//FB 3.3.0, 3.2.0 - 3.2.4, 3.1.0 - 3.1.12, 3.0.x and prior Purity//FB releases are vulnerable to possibly exposed credentials for accessing the product’s management interface. The password may be known outside Pure Storage and could be used on an affected system, if reachable, to execute arbitrary instructions with root privileges. No other Pure Storage products or services are affected. Remediation is available from Pure Storage via a self-serve “opt-in” patch, manual patch application or a software upgrade to an unaffected version of Purity software.

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

Hardcoded/embedded credentials vulnerability in Pure Storage FlashArray and FlashBlade management interfaces. The administrative password may be publicly known, allowing unauthenticated attackers to gain root-level access to affected storage systems.

MitigationApply the available opt-in patch, manually patch, or upgrade to an unaffected Purity software version per Pure Storage's guidance.

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.3.18>= 6.0.0, < 6.0.9>= 6.1.0, < 6.1.13>= 6.2.0, < 6.2.4
Purity\/\/fbApplication
Affected:< 3.1.13>= 3.2.0, < 3.2.5>= 3.3.0, < 3.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 your Pure Storage product type
    Determine whether the system is a FlashArray (Purity//fa) or FlashBlade (Purity//fb). This can be done via the system GUI, CLI (purectl info), or management interface.
    Affected if System is either FlashArray or FlashBlade with management interface accessible
  2. Determine installed Purity//fa version (FlashArray)
    Run command 'purectl version' or access the management GUI to view the Purity software version. On FlashArray, use 'purefa get -g' or check the GUI dashboard for the version string.
    Affected if Version is < 5.3.18, or >= 6.0.0 and < 6.0.9, or >= 6.1.0 and < 6.1.13, or >= 6.2.0 and < 6.2.4
  3. Determine installed Purity//fb version (FlashBlade)
    Run command 'pureblt version' or access the management GUI to view the Purity software version. On FlashBlade, use 'purefb get' or check the GUI dashboard for the version string.
    Affected if Version is < 3.1.13, or >= 3.2.0 and < 3.2.5, or >= 3.3.0 and < 3.3.1
  4. Verify management interface accessibility
    Confirm the management interface (GUI or CLI) is exposed to the network. Check firewall rules and access controls governing the Pure Storage admin port (typically 443).
    Affected if Management interface is reachable from untrusted networks

If the installed Purity version falls within any of the affected version ranges and the management interface is network-accessible, the system is vulnerable to unauthenticated root access via the hardcoded credential.

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 3.1.13 / 3.2.5 / 3.3.1 or later
Fixed in 3.1.133.2.53.3.1
Interim mitigation

Apply the available opt-in patch, manually patch, or upgrade to an unaffected Purity software version per Pure Storage's guidance.

Recommended fix High confidence

Purity//FA: 5.3.18+ / 6.0.9+ / 6.1.13+ / 6.2.4+; Purity//FB: 3.1.13+ / 3.2.5+ / 3.3.1+

  1. 1. Identify whether the system is FlashArray (Purity//FA) or FlashBlade (Purity//FB)
  2. 2. For Purity//FA: upgrade to version 5.3.18, 6.0.9, 6.1.13, 6.2.4 or later
  3. 3. For Purity//FB: upgrade to version 3.1.13, 3.2.5, 3.3.1 or later
  4. 4. Alternatively, apply the self-serve opt-in patch or manual patch provided by Pure Storage support (support.purestorage.com)
  5. 5. After upgrade, change the management interface password immediately as a security best practice
  6. 6. Verify the upgrade was successful and the vulnerability is resolved
Caveat Pure Storage recommends scheduling maintenance window as upgrades may require brief system downtime; verify compatibility with any connected systems

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

Fix this in Purity\/\/fa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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