CVE-2025-46371
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) a Use of a Broken or Risky Cryptographic Algorithm vulnerability in the ssh. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Protection mechanism bypass.
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 below contain a Use of a Broken or Risky Cryptographic Algorithm vulnerability in the SSH service. A low-privileged attacker with local system access could exploit weak or deprecated cryptographic primitives in the SSH implementation to bypass protection mechanisms.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 versionCheck the installed version of Dell PowerFlex Manager, PowerFlex Appliance Intelligent Catalog, or PowerFlex Rack using the system's version check command or by inspecting the software inventory. For PowerFlex Manager, look in the management interface or system documentation for the version number.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 SSH service configurationIdentify the SSH daemon configuration file on the affected system. This is typically /etc/ssh/sshd_config but may vary based on the PowerFlex deployment model. Check both the primary management node and any compute nodes.Affected if The SSH configuration file exists on the system, which is required for the vulnerability to be present.
-
Inspect SSH cryptographic algorithm settingsExamine the SSH configuration for cipher, mac, and kex algorithms. Look for deprecated or weak algorithms such as 3des-cbc, aes128-cbc, aes192-cbc, sha1, or diffie-hellman-group14-sha1. Use 'sshd -T' or manually inspect the config file to list enabled algorithms.Affected if Weak or deprecated cryptographic algorithms (e.g., older block ciphers like aes128-cbc, weak hash algorithms like sha1, or outdated key exchange methods) are enabled in the SSH configuration
-
Check for disabled strong algorithmsVerify whether strong modern algorithms are missing or explicitly disabled. Confirm whether strong ciphers ([email protected], aes256-ctr), strong MACs (hmac-sha2-256, hmac-sha2-512), and strong key exchange (curve25519-sha256, ecdh-sha2-nistp256) are either absent or commented out in favor of weaker options.Affected if Strong modern cryptographic algorithms are not configured or are explicitly disabled, leaving only weak algorithms in use
A system is affected if it runs any of the listed product versions AND SSH is configured with weak or deprecated cryptographic algorithms that could be bypassed by an attacker with local access.
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 data3.7.8.048.383.00
Upgrade Dell PowerFlex Manager to a version beyond 4.6.2 that contains the patched SSH cryptographic implementation, or review and harden SSH configuration to use only strong, modern cryptographic algorithms.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46371 — 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-46371 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