dbcve.org
Mlnx OsOperating system · Nvidia

CVE-2024-0101

HIGH · 7.5 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 3.10.4402 / 3.11.2002 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
NVIDIA Mellanox OS, ONYX, Skyway, MetroX-2 and MetroX-3 XC contain a vulnerability in ipfilter, where improper ipfilter definitions could enable an attacker to cause a failure by attacking the switch. A successful exploit of this vulnerability might lead to denial of service.

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

NVIDIA Mellanox switch operating systems (Mellanox OS, ONYX, Skyway, MetroX-2/3 XC) contain a vulnerability in the ipfilter packet filtering component. Improperly configured or malformed ipfilter definitions can be exploited by an attacker to cause switch failure, resulting in denial of service. The vulnerability stems from insufficient validation or incorrect rule definitions within the switch's firewall/packet filtering logic.

MitigationReview and correct all ipfilter rule definitions on affected switches to ensure proper validation and remove any malformed rules. Consider updating to vendor-provided patches and verifying ipfilter configuration integrity.

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
Mlnx OsOperating system
Affected:< 3.11.2002
Mlnx GwOperating system
Affected:< 8.1.4400< 8.2.2000
OnyxOperating system
Affected:< 3.10.4402
Nvda Os XcOperating system
Affected:< 18.2.2000

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

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

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. Identify the switch OS and version
    Run 'show version' or 'show system' to determine the installed OS type (Mellanox OS, ONYX, MLNX-GW, or NVDA OS XC) and exact version number
    Affected if The OS version falls below 3.11.2002 for Mellanox OS, below 8.1.4400 or 8.2.2000 for MLNX-GW, below 3.10.4402 for ONYX, or below 18.2.2000 for NVDA OS XC
  2. Verify ipfilter is enabled
    Run 'show ipfilter status' or 'show running-config ipfilter' to determine if the ipfilter packet filtering feature is currently active on the switch
    Affected if ipfilter is enabled and actively processing traffic
  3. Review ipfilter rule definitions
    Run 'show ipfilter' or 'show ipfilter rules' to display all configured ipfilter rules. Inspect each rule definition for malformed syntax, missing required fields, invalid source/destination specifications, or improperly configured rule parameters
    Affected if Any ipfilter rule definitions are malformed, improperly configured, or contain invalid syntax that could trigger insufficient validation in the packet filtering logic

The switch is vulnerable if it runs an affected OS version AND has ipfilter enabled with potentially malformed or improperly validated rule definitions.

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 3.10.4402 / 3.11.2002 / 8.1.4400 or later
Fixed in 3.10.44023.11.20028.1.4400
Interim mitigation

Review and correct all ipfilter rule definitions on affected switches to ensure proper validation and remove any malformed rules. Consider updating to vendor-provided patches and verifying ipfilter configuration integrity.

Recommended fix High confidence

Mlnx OS >= 3.11.2002 | Mlnx GW >= 8.2.2000 (or 8.1.4400+ for 8.1 branch) | ONYX >= 3.10.4402 | Nvda OS XC >= 18.2.2000

  1. 1. Identify the affected product (Mlnx OS, Mlnx GW, ONYX, or Nvda OS XC) running in your environment
  2. 2. Document the current installed version using the product's CLI (e.g., 'show version' or 'show boot')
  3. 3. For Mlnx OS: Schedule maintenance window and upgrade to version 3.11.2002 or later
  4. 4. For Mlnx GW: Upgrade to version 8.2.2000 or later (if running 8.1.x branch, upgrade to 8.1.4400 or later; if running 8.2.x, upgrade to 8.2.2000 or later)
  5. 5. For ONYX: Upgrade to version 3.10.4402 or later
  6. 6. For Nvda OS XC: Upgrade to version 18.2.2000 or later
  7. 7. After upgrade, verify ipfilter configuration is correct using 'show ipfilter' and review firewall rules
  8. 8. Test normal traffic flows to confirm the switch operates normally post-upgrade
Caveat Review NVIDIA release notes for your specific product to check for configuration syntax changes or feature deprecations between your current version and the target fixed version

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

Fix this in Mlnx Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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