CVE-2024-0005: A condition exists in FlashArray and FlashBlade Purity whereby a malicious user could execute arbitrary comman

This month

CRITICAL 9.1UPGRADEUPGRADE

CVE-2024-0005 is a critical-severity flaw (CVSS 9.1) affecting purity\/\/fa, purity\/\/fb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A condition exists in FlashArray and FlashBlade Purity whereby a malicious user could execute arbitrary commands remotely through a specifically crafted SNMP configuration.

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.1 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-77
Published	2024-09-23
Last modified	2026-06-17

Publisher (CNA): Pure Storage, Inc. · Vendor: purestorage

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-23 18:15 UTCPublished CVE record published
2026-06-17 06:52 UTCUpdated Record last modified

purestorage purity\/\/fa UPGRADE

Affected: >= 5.0.0 and <= 5.0.11 · >= 5.1.0 and <= 5.1.17 · >= 5.2.0 and <= 5.2.7 · >= 5.3.0 and <= 5.3.21 · >= 6.0.0 and <= 6.0.9 · >= 6.1.0 and <= 6.1.25 · >= 6.2.0 and <= 6.2.17 · >= 6.3.0 and <= 6.3.14

Fixed in: newer than 6.4.10

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy purityfa || rpm -q purityfa || purityfa --version

2. UPGRADE to newer than 6.4.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade purityfa

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade purityfa

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison purityfa sudo apt install purityfa=<VERSION_BEFORE_5.0.0> sudo apt-mark hold purityfa

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list purityfa sudo dnf downgrade purityfa-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add purityfa

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

purestorage purity\/\/fb UPGRADE

Affected: >= 3.0.0 and <= 3.0.9 · >= 3.1.0 and <= 3.1.5 · >= 3.2.0 and <= 3.2.10 · >= 3.3.0 and <= 3.3.11 · >= 4.0.0 and <= 4.0.6 · >= 4.1.0 and <= 4.1.10 · >= 4.2.0 and <= 4.2.3 · 4.3.0

Fixed in: newer than 4.2.3

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy purityfb || rpm -q purityfb || purityfb --version

2. UPGRADE to newer than 4.2.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade purityfb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade purityfb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison purityfb sudo apt install purityfb=<VERSION_BEFORE_3.0.0> sudo apt-mark hold purityfb

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list purityfb sudo dnf downgrade purityfb-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add purityfb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-0005?

purity\/\/fa: upgrade to newer than 6.4.10; purity\/\/fb: upgrade to newer than 4.2.3. Exact commands for each OS are on this page.

Is CVE-2024-0005 being exploited?

CVE-2024-0005 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-0005 affect?

CVE-2024-0005 affects purity\/\/fa, purity\/\/fb. Severity is critical (CVSS 9.1). A condition exists in FlashArray and FlashBlade Purity whereby a malicious user could execute arbitrary commands remotely through a specifically crafted SNMP configuration.

How urgent is CVE-2024-0005?

Priority 44/100. Critical severity

Related CVEs

CVE-2024-0004 CRITICAL 9.1 UPGRADE A condition exists in FlashArray Purity whereby an user with array admin role can execute arbitrary commands r
CVE-2024-0003 CRITICAL 9.1 UPGRADE A condition exists in FlashArray Purity whereby a malicious user could use a remote administrative service to
CVE-2024-0002 CRITICAL 10.0 UPGRADE A condition exists in FlashArray Purity whereby an attacker can employ a privileged account allowing remote ac
CVE-2024-0001 CRITICAL 10.0 UPGRADE A condition exists in FlashArray Purity whereby a local account intended for initial array configuration remai

References

← Back to latest CVEs