Networking Os10Operating system · Dell

CVE-2024-25949

HIGH · 8.8 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to 10.5.3.10 / 10.5.4.11 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 OS10 Networking Switches, versions10.5.6.x, 10.5.5.x, 10.5.4.x and 10.5.3.x ,contain an improper authorization vulnerability. A remote authenticated attacker could potentially exploit this vulnerability leading to escalation of 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
How this class of weakness works · CWE-285

The application confirms who you are but does not properly check whether you are permitted to perform a given action, so authenticated users reach functions or data meant for others. Attackers test roles and object references to find the gap. Remediation is an authorization check on every request, evaluated against the acting user's actual permissions.

General guidance for the improper authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Networking Os10Operating system
Affected:>= 10.5.3.0, < 10.5.3.10>= 10.5.4.0, < 10.5.4.11>= 10.5.5.0, < 10.5.5.8= 10.5.6.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 10.5.3.10 / 10.5.4.11 / 10.5.5.8 or later
Fixed in 10.5.3.1010.5.4.1110.5.5.8
Vendor patch www.dell.com →
Recommended fix High confidence

Minimum fixed versions: 10.5.3.10 (for 10.5.3.x branch), 10.5.4.11 (for 10.5.4.x branch), 10.5.5.8 (for 10.5.5.x branch), or a version >10.5.6.0 (for 10.5.6.0)

  1. Verify the current OS10 version using 'show version' command
  2. Identify the appropriate target version based on current branch: for 10.5.3.x upgrade to 10.5.3.10, for 10.5.4.x upgrade to 10.5.4.11, for 10.5.5.x upgrade to 10.5.5.8, for 10.5.6.0 upgrade to a later patched release
  3. Download the required software image from Dell support portal (support.dell.com)
  4. Back up current configuration using 'copy running-config startup-config' or 'write memory'
  5. Transfer the new OS image to the switch using SCP, FTP, or USB as appropriate
  6. Install the new image using 'software install <image-name>' command
  7. Reboot the switch using 'reload' command
  8. After reboot, verify the new version is running using 'show version' and confirm the vulnerability is resolved
Caveat Dell minor version updates within the same branch typically maintain configuration compatibility; verify release notes for any specific caveats

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25949 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25949 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