CVE-2025-32746
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 PowerFlex Manager, version(s) <=4.6.2, contain(s) an Insecure Storage of Sensitive Information vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to unauthorized access to sensitive information.
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 PowerFlex Manager versions 4.6.2 and earlier contain an insecure storage vulnerability where sensitive information is stored without adequate protection. An unauthenticated attacker with local system access could exploit this to read sensitive data that should have been encrypted or otherwise secured.
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< 48.383.00<= 4.6.2< 3.7.8.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 PowerFlex product and versionCheck the system inventory or installed packages for Dell PowerFlex Manager, PowerFlex Appliance Intelligent Catalog, or PowerFlex Rack. Use the vendor-provided version check tool or look in /opt/dell/powerflex or similar installation directories for a version file.Affected if The installed version is Dell Powerflex Manager <= 4.6.2, Powerflex Appliance Intelligent Catalog < 48.383.00, or Powerflex Rack < 3.7.8.0
-
Locate configuration files that may contain stored credentialsSearch common configuration directories such as /etc, /opt, or application data folders for files like config.json, application.properties, secrets.xml, or .env files. Use commands like 'find / -name "*.conf" -o -name "*.properties" -o -name "*.xml"' focusing on the PowerFlex installation directory.Affected if Plaintext usernames, passwords, API keys, or tokens are found in any configuration files within the PowerFlex installation or data directories
-
Inspect the database or credential storage for weak encryptionExamine any embedded databases (SQLite, MySQL, PostgreSQL) or credential vaults used by PowerFlex. Check the encryption method used for sensitive tables or files. Look for base64-encoded strings, DES encryption, or custom obfuscation instead of strong AES or industry-standard encryption.Affected if Credentials are stored using reversible encoding, weak symmetric encryption, or no encryption at all in database tables or storage files
-
Review log files for plaintext secretsCheck application logs in /var/log or the PowerFlex log directory for entries containing passwords, keys, or tokens. Search log files for patterns like 'password=', 'apikey=', 'secret=', or 'token='.Affected if Sensitive credentials or keys appear in plaintext within log files accessible to local users
-
Verify file permissions on sensitive configuration filesCheck permissions on configuration files containing potential secrets using 'ls -la'. Verify that only root or the application service account can read sensitive files, not world-readable or group-readable.Affected if Configuration files containing credentials are readable by unprivileged local users due to overly permissive file permissions
A user is affected if they are running any of the listed product versions AND any plaintext credentials, weakly encrypted secrets, or unprotected sensitive data are found in configuration files, databases, or logs within the PowerFlex installation.
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 · scoped3.7.8.048.383.00
Upgrade to a patched version of Dell PowerFlex Manager when available. In the interim, restrict local access to the system and audit storage locations for unprotected sensitive data.
PowerFlex Appliance Intelligent Catalog: >=48.383.00 | PowerFlex Manager: >4.6.2 (e.g., 4.7.0) | PowerFlex Rack: >=3.7.8.0
- 1. Identify the specific PowerFlex product in your environment (Appliance Intelligent Catalog, Manager, or Rack)
- 2. For PowerFlex Appliance Intelligent Catalog: upgrade to version 48.383.00 or later
- 3. For PowerFlex Manager: upgrade to version 4.7.0 or later (the first version greater than 4.6.2)
- 4. For PowerFlex Rack: upgrade to version 3.7.8.0 or later
- 5. Verify the upgrade was successful by confirming the installed version matches or exceeds the fixed version
- 6. Test that PowerFlex functionality remains operational after the upgrade
- 7. Review system logs to confirm no unauthorized access occurred prior to remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32746 — 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-32746 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