CVE-2024-3057
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 · uneditedA flaw exists whereby a user can make a specific call to a FlashArray endpoint allowing privilege escalation.
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 · moderate confidenceA privilege escalation vulnerability exists in Pure Storage FlashArray where a specific API endpoint call allows an authenticated user to elevate their privileges beyond what their role should permit. The vulnerability enables bypassing normal authorization controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Pure Storage FlashArray systemIdentify the system by querying the API endpoint /api/1.0/array or running command purectl list to retrieve system model and version informationAffected if System is not a Pure Storage FlashArray (vulnerability applies only to this product)
-
Check REST API service statusVerify the FlashArray REST API service is running and accessible on the management interface (default port 443). Use curl -k https://<array-ip>/api/1.0/array to test connectivityAffected if REST API is not exposed or accessible - the vulnerability requires API endpoint access
-
Identify users with API authenticationQuery authorized API users via /api/1.0/authorization/users endpoint or command pureadmin list. Document which users have API credentialsAffected if No users possess API credentials - the vulnerability requires an authenticated user to exploit
-
Review user role assignmentsEnumerate current user roles and permissions using /api/1.0/authorization/roles or pureadmin list --role. Compare assigned roles against expected baseline permissionsAffected if Users have roles that permit access to the vulnerable API endpoint enabling privilege escalation
-
Compare installed version to vendor advisoriesRetrieve the exact FlashArray version via /api/1.0/array or purectl list and cross-reference with Pure Storage security advisory for CVE-2024-3057 to determine if version falls within affected rangeAffected if Installed version is within the range identified by Pure Storage as vulnerable
A user is affected if they have authenticated API access to a FlashArray version within the affected range, where the vulnerable endpoint permits bypassing role-based authorization controls to escalate privileges.
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.
From vendor dataApply the vendor-provided patch for FlashArray. If a patch is unavailable, restrict network access to the FlashArray management interfaces to trusted IP addresses and ensure users are assigned only the minimum necessary privileges.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3057 — 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-2024-3057 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