CVE-2025-36572
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 · uneditedDell PowerStore, version(s) 4.0.0.0, contain(s) an Use of Hard-coded Credentials vulnerability in the PowerStore image file. A low privileged attacker with remote access, with the knowledge of the hard-coded credentials, could potentially exploit this vulnerability to gain unauthorized access based on the hardcoded account's privileges.
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 confidenceDell PowerStore version 4.0.0.0 contains hardcoded credentials embedded within the PowerStore image file. A low-privileged attacker with remote network access and knowledge of these credentials can authenticate to the system using the hardcoded account's privileges, potentially bypassing normal authentication controls.
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< 4.0.1.3-2494147CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 the installed PowerStoreos versionAccess the PowerStore management interface or use the 'psutil' command-line tool (if available) to retrieve the current firmware/OS version. Typical commands include 'psutil -version' or checking via the UI under Settings > About.Affected if The installed version is lower than 4.0.1.3-2494147 (e.g., 4.0.0.0 as listed in the summary).
-
Verify remote management access is enabledCheck the PowerStore network configuration settings to determine if remote management interfaces (such as the REST API, SSH, or the management GUI) are exposed to the network. Look for accessible IP addresses or network binding configurations.Affected if Remote network access to PowerStore management interfaces is enabled and reachable from untrusted networks.
-
Review user accounts for unauthorized or unexpected entriesUse the PowerStore administrative UI or CLI to list all local user accounts. Compare the list against documented, expected accounts. Look for any account that was not created by your administrative team.Affected if Any local user account exists that was not explicitly created by your organization or matches known legitimate accounts.
-
Examine authentication and access logs for suspicious activityReview PowerStore audit logs, authentication logs, and access records for successful logins from IP addresses or accounts that your team does not recognize. Check for login events occurring outside of normal administrative windows.Affected if Logs show successful authentications using credentials or accounts that your organization did not create or authorize.
A user is affected if their PowerStoreos version is below 4.0.1.3-2494147 and remote management access is enabled, creating conditions where the hardcoded credentials could be exploited by an attacker.
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 · scoped4.0.1.3-2494147
Contact Dell support to obtain the official patch or firmware update that addresses this hardcoded credential vulnerability. Rotate any credentials that may have been exposed and review access logs for unauthorized use.
PowerStoreOS version 4.0.1.3-2494147 or later
- 1. Identify the current PowerStoreOS version by accessing the PowerStore management interface or running the appropriate system inventory command
- 2. Navigate to Dell's official support website (www.dell.com) or contact Dell PowerStore support to obtain the version 4.0.1.3-2494147 or later update package
- 3. Download the verified PowerStoreOS update package from Dell's official support channels
- 4. Follow Dell's documented PowerStore upgrade procedure, which typically involves: uploading the update bundle to the PowerStore system, validating the update package integrity, scheduling a maintenance window, and applying the update through the PowerStore management UI or CLI
- 5. After upgrade completion, verify the new PowerStoreOS version is 4.0.1.3-2494147 or higher using the management interface
- 6. As a security best practice following this hard-coded credential fix, change any default or shared credentials that may have been exposed and ensure proper credential management policies are in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36572 — 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-2025-36572 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