dbcve.org
Powerflex ManagerApplication · Dell

CVE-2025-36599

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 4.6.2.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Dell PowerFlex Manager VM, versions prior to 4.6.2.1, contains an Insertion of Sensitive Information into Log File vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to the disclosure of certain user credentials. The attacker may be able to use the exposed credentials to access the system with privileges of the compromised account.

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 · high confidence

Dell PowerFlex Manager VM versions prior to 4.6.2.1 contain a vulnerability where sensitive user credentials are written to log files. A low-privileged attacker with remote access can exploit this to read the exposed credentials and gain unauthorized access to the system with the privileges of the compromised account.

MitigationUpgrade Dell PowerFlex Manager VM to version 4.6.2.1 or later. Additionally, review existing log files for any exposed credentials and rotate compromised credentials as a precautionary measure.

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
Powerflex ManagerApplication
Affected:< 4.6.2.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Dell PowerFlex Manager VM is installed
    Locate and identify the Dell PowerFlex Manager VM installation in your environment. This may be found in your virtualization or infrastructure inventory systems.
    Affected if The system is running Dell PowerFlex Manager VM and the version is prior to 4.6.2.1
  2. Determine the installed version
    Use system inventory tools, check the VM configuration, or query the PowerFlex Manager interface to obtain the exact version number. Compare this version against the vulnerable range of versions prior to 4.6.2.1.
    Affected if The installed version is anything less than 4.6.2.1
  3. Identify log file locations
    Locate the log directories used by Dell PowerFlex Manager VM. These are typically found within the VM's filesystem under the installation or service directories.
    Affected if Log files exist and are accessible to be inspected
  4. Search log files for credential patterns
    Examine PowerFlex Manager log files for strings that may contain credentials, passwords, or authentication tokens. Look for patterns such as 'password=', 'pwd=', 'credential=', or similar authentication-related keywords in plain text.
    Affected if Log files contain any readable user credentials or authentication strings in plain text
  5. Assess remote access exposure
    Determine if the PowerFlex Manager VM is accessible remotely over the network. Review network access controls, firewall rules, and authentication mechanisms protecting the interface.
    Affected if The VM is network-accessible to low-privileged users or unauthenticated attackers

You are affected if Dell PowerFlex Manager VM version is below 4.6.2.1 and log files contain exposed credentials that could be accessed by a low-privileged remote attacker.

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.

dbcve · scoped
Upgrade available Upgrade to 4.6.2.1 or later
Fixed in 4.6.2.1
Interim mitigation

Upgrade Dell PowerFlex Manager VM to version 4.6.2.1 or later. Additionally, review existing log files for any exposed credentials and rotate compromised credentials as a precautionary measure.

Recommended fix High confidence

4.6.2.1 or later

  1. Verify current PowerFlex Manager version through the management interface or system inventory
  2. Schedule a maintenance window for the upgrade process
  3. Back up all critical data, configurations, and the current system state
  4. Obtain the PowerFlex Manager 4.6.2.1 or later version from Dell support (support.dell.com)
  5. Follow Dell's documented upgrade procedure for PowerFlex Manager, typically involving uploading the upgrade package through the management interface
  6. Complete the upgrade and verify the new version is 4.6.2.1 or later
  7. Validate that the system is functioning correctly post-upgrade
  8. Review system logs to confirm no sensitive information is being written to log files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerflex Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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