dbcve.org
NetworkerApplication · Dell

CVE-2025-36582

HIGH · 7.5 CVSS v3.1 Published 2025-07-01
Fix available
A fix is available. Upgrade to 19.13 or later.
See remediation →
84/100
Remediation priority · High
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
Dell NetWorker, versions 19.12.0.1 and prior, contains a Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information disclosure.

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

Dell NetWorker versions 19.12.0.1 and prior contain an algorithm downgrade vulnerability where the system accepts less-secure cryptographic algorithms during negotiation. An unauthenticated remote attacker could exploit this to force the use of weak cryptographic algorithms, potentially leading to information disclosure through crypto attacks on the weakened session.

MitigationRemediate by disabling weak/legacy cryptographic algorithms (e.g., SSLv2/v3, TLS 1.0/1.1, weak ciphers) in NetWorker configuration and enforcing strong cipher suites. If available, upgrade to a patched NetWorker version.

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
NetworkerApplication
Affected:< 19.13

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine NetWorker version
    Run 'nsrversion -v' or check the installed NetWorker package version using the system's package manager
    Affected if Installed version is 19.12.0.1 or prior (anything below 19.13)
  2. Locate NetWorker cryptographic configuration
    Search for NetWorker configuration files related to SSL/TLS settings, typically found in the NetWorker install directory or configuration directories (e.g., nsr/, /nsr/config/)
    Affected if Weak cryptographic algorithms (SSLv2, SSLv3, TLS 1.0, TLS 1.1) or weak cipher suites are explicitly enabled in the configuration
  3. Inspect TLS protocol settings
    Examine the NetWorker configuration for allowed protocols - look for parameters controlling SSL/TLS version negotiation such as 'min_tls_version', 'allow_tls_1.0', 'legacy_ssl', or similar settings
    Affected if TLS 1.0 or TLS 1.1 is permitted or if the system defaults allow protocol downgrade
  4. Review enabled cipher suites
    Check NetWorker cipher configuration for allowed encryption algorithms - look for 'cipher_list', 'ciphers', or 'allowed_ciphers' parameters and identify any weak or export-grade ciphers (e.g., NULL, 3DES, RC4, MD5-based)
    Affected if Weak or export-grade ciphers are included in the allowed cipher list

You are affected if your NetWorker version is below 19.13 AND weak cryptographic algorithms or protocol versions are enabled in the NetWorker configuration, allowing an attacker to force negotiation of insecure crypto settings.

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 19.13 or later
Fixed in 19.13
Interim mitigation

Remediate by disabling weak/legacy cryptographic algorithms (e.g., SSLv2/v3, TLS 1.0/1.1, weak ciphers) in NetWorker configuration and enforcing strong cipher suites. If available, upgrade to a patched NetWorker version.

Recommended fix Moderate confidence

19.13

  1. 1. Review the Dell NetWorker 19.13 release notes for any prerequisites or compatibility considerations.
  2. 2. Ensure you have a complete backup of your NetWorker configuration and database.
  3. 3. Schedule a maintenance window for the upgrade procedure.
  4. 4. Download Dell NetWorker version 19.13 or later from the Dell support portal.
  5. 5. Stop all NetWorker services on the server before beginning the upgrade.
  6. 6. Install the NetWorker 19.13 package using the standard upgrade procedure.
  7. 7. Verify that all NetWorker services start successfully after the upgrade.
  8. 8. Confirm the NetWorker version is now 19.13 or later using the 'nsrversion -v' command.
Caveat Review Dell NetWorker 19.13 release notes for any configuration or compatibility changes

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

Fix this in Networker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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