CVE-2024-0001: Critical severity pure storage purity vulnerability

Published Sep 23, 2024
·
Updated

A condition exists in FlashArray Purity whereby a local account intended for initial array configuration remains active potentially allowing a malicious actor to gain elevated privileges.

Affected Software

2 affected components
PureStorage Purity\/\/fa>=6.3.0<=6.3.14
PureStorage Purity\/\/fa>=6.4.0<=6.4.10

Remediation

Information

Affected customers will need to apply a self-service patch bundle or upgrade their Purity to an unaffected Purity version. This issue is resolved in the following FlashArray Purity releases: * Purity//FA versions 6.3.15 or later  * Purity//FA versions 6.5.1 or later  * Purity//FA versions 6.6.1 or later.

Event History

Sep 23, 2024
CVE Published
via MITRE·05:25 PM
Data Sourced
via MITRE·05:25 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-0001?

CVE-2024-0001 has been classified as a high severity vulnerability due to the potential for unauthorized elevated privileges.

2

How do I fix CVE-2024-0001?

To remediate CVE-2024-0001, disable the local account used for initial array configuration if it is still active.

3

Which versions of Purestorage Purity are affected by CVE-2024-0001?

CVE-2024-0001 affects Purestorage Purity versions from 6.3.0 to 6.3.14 and from 6.4.0 to 6.4.10.

4

What are the potential risks associated with CVE-2024-0001?

The risk associated with CVE-2024-0001 includes the possibility of a malicious actor gaining unauthorized access and control over the affected storage array.

5

Who reported CVE-2024-0001?

CVE-2024-0001 was reported by the security team at Pure Storage as part of their ongoing security assessment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203