CVE-2022-32552
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 · uneditedPure 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 a privilege escalation via the manipulation of Python environment variables which can be exploited by a logged-in user to escape a restricted shell to an unrestricted shell 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 confidencePure Storage FlashArray and FlashBlade products contain a privilege escalation vulnerability where authenticated users can manipulate Python environment variables to escape a restricted shell and gain root-level privileges. This allows any logged-in user to escalate from their constrained shell access to full unrestricted administrative access.
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< 5.3.18>= 6.0.0, < 6.0.9>= 6.1.0, < 6.1.13>= 6.2.0, < 6.2.4< 3.1.13>= 3.2.0, < 3.2.5>= 3.3.0, < 3.3.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Purity//fa versionAccess the Pure Storage FlashArray management interface or use the Pure CLI (`purectl version` or `purefa get -s`) to retrieve the installed Purity//fa software versionAffected if The version falls within < 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
-
Identify Purity//fb versionAccess the Pure Storage FlashBlade management interface or use the Pure CLI (`pureblades version` or `purefb get -s`) to retrieve the installed Purity//fb software versionAffected if The version falls within < 3.1.13 OR >= 3.2.0 and < 3.2.5 OR >= 3.3.0 and < 3.3.1
-
Confirm authenticated user access existsReview user accounts that have shell access to the Pure Storage array. Check if any non-administrative users have login credentials for the restricted shell environmentAffected if Any authenticated users exist with access to the restricted shell on the affected device
-
Verify Python environment variable manipulation is possibleFrom the restricted shell session, attempt to set or modify Python-related environment variables such as PYTHONPATH, PYTHONHOME, or PYTHONSTARTUP. If the restricted shell permits modification of these variables, the condition is metAffected if The restricted shell allows manipulation of Python environment variables without blocking such modifications
The environment is affected if the installed Purity//fa or Purity//fb version matches any of the affected version ranges AND authenticated users have access to the restricted shell where Python environment variables can be manipulated.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.133.2.53.3.1
Apply the self-serve opt-in patch, manually apply the vendor patch, or upgrade to an unaffected version of Purity//FA or Purity//FB software as specified in Pure Storage advisory.
Purity//FA: upgrade to 5.3.18, 6.0.9, 6.1.13, or 6.2.4 (or later); Purity//FB: upgrade to 3.1.13, 3.2.5, or 3.3.1 (or later)
- 1. Identify the current Purity//FA or Purity//FB version running on your FlashArray or FlashBlade device.
- 2. For Purity//FA: If running version 5.2.x or prior, upgrade to 5.3.18 or later. If running 5.3.0-5.3.17, upgrade to 5.3.18. If running 6.0.0-6.0.8, upgrade to 6.0.9 or later. If running 6.1.0-6.1.12, upgrade to 6.1.13 or later. If running 6.2.0-6.2.3, upgrade to 6.2.4 or later.
- 3. For Purity//FB: If running version 3.0.x or prior, upgrade to 3.1.13 or later. If running 3.1.0-3.1.12, upgrade to 3.1.13. If running 3.2.0-3.2.4, upgrade to 3.2.5. If running 3.3.0, upgrade to 3.3.1.
- 4. Contact Pure Storage support to obtain the self-serve opt-in patch, manual patch, or upgrade package from support.purestorage.com.
- 5. Schedule maintenance window as upgrade may require downtime.
- 6. Apply the patch or perform the upgrade following Pure Storage documentation.
- 7. Verify the version has been updated and the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-32552 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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