dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-0052

HIGH · 8.3 CVSS v4.0 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/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
Improper input validation performed during the authentication process of FlashBlade could lead to a system Denial of Service.

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 confidence

This is an improper input validation vulnerability in the authentication process of Pure Storage FlashBlade systems. During authentication, the system fails to properly validate input, which can be exploited to cause a system-wide Denial of Service.

MitigationApply the vendor-provided patch or firmware update from Pure Storage for FlashBlade, as this is a code-level fix requiring vendor release. Test authentication functionality thoroughly after applying the update.

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
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Pure Storage FlashBlade systems in your environment
    Inventory your storage infrastructure and confirm any Pure Storage FlashBlade arrays. Check for FlashBlade management interfaces, APIs, or CLI tools (fbos, purefb) that indicate FlashBlade presence.
    Affected if You have any Pure Storage FlashBlade systems deployed in your environment.
  2. Determine the FlashBlade firmware version
    Access the FlashBlade management interface (GUI or CLI using 'purefb info' or API call to /api/2.0/arrays) and record the installed firmware version. Compare this version against the vendor patch release for CVE-2025-0052.
    Affected if The installed firmware version is lower than the patched version released by Pure Storage for this CVE.
  3. Verify the authentication service is enabled and accessible
    Check if the FlashBlade authentication service (local user authentication, LDAP/AD integration, or API access) is configured and reachable. Review authentication settings via 'purefb auth' CLI or API endpoint /api/2.0/local/ users.
    Affected if Authentication is enabled and the array is network-accessible (the vulnerability is in the authentication path).
  4. Check for authentication-related service degradation
    Monitor system logs (/var/log/messages, FlashBlade audit logs) for authentication failures, input validation errors, or service instability related to the authentication endpoint. Look for patterns indicating DoS conditions.
    Affected if Authentication service shows instability, excessive failures, or input validation errors in logs.

Your environment is affected if you run a Pure Storage FlashBlade system with authentication enabled and the firmware version is below the vendor patched version for CVE-2025-0052.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patch or firmware update from Pure Storage for FlashBlade, as this is a code-level fix requiring vendor release. Test authentication functionality thoroughly after applying the update.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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