dbcve.org
Mlnx OsOperating system · Nvidia

CVE-2024-0113

HIGH · 8.8 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 3.10.4500 / 3.10.4504 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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, and MetroX-3 XCC contain a vulnerability in the web support, where an attacker can cause a CGI path traversal by a specially crafted URI. A successful exploit of this vulnerability might lead to escalation of privileges and 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

Path traversal vulnerability in the web CGI component of NVIDIA Mellanox networking firmware (OS, ONYX, Skyway, MetroX-3 XCC). Specially crafted URIs allow attackers to traverse directory structures, potentially accessing sensitive files and escalating privileges.

MitigationApply vendor-supplied firmware patches when available; restrict web management interface access to trusted networks and implement URI filtering/monitoring to detect traversal attempts.

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.10.4500< 3.12.1002>= 3.11.0000, < 3.11.2302
OnyxOperating system
Affected:< 3.10.4504
Mlnx GwOperating system
Affected:< 8.1.4500< 8.2.2300
Nvda Os XcOperating system
Affected:< 18.2.2200

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 installed firmware version
    Run 'show version' or 'get version' command via CLI, or check the web interface login page for version display
    Affected if The version number is lower than any of these: MLNX OS < 3.10.4500, < 3.12.1002, or < 3.11.2302; Onyx < 3.10.4504; MLNX GW < 8.1.4500 or < 8.2.2300; NVDA OS XC < 18.2.2200
  2. Confirm the product variant
    Run 'show system' or 'get product' to identify whether the device runs MLNX OS, Onyx, MLNX GW, or NVDA OS XC
    Affected if The device is any of the affected product variants listed in the version ranges above
  3. Verify the web CGI service is enabled
    Check via CLI: 'show web' or 'show http server' to see if the web management interface (CGI) is active
    Affected if The web CGI component is enabled and running on the device
  4. Check web interface accessibility
    Attempt to reach the device web interface via browser at http://<device-ip> or check firewall rules: 'show ip http' or 'show firewall policy' for http/https ports 80/443
    Affected if The web management interface is exposed and reachable from a network segment accessible to potential attackers

You are affected if your device runs one of the affected product variants with a version lower than the patched releases AND the web CGI component is enabled and accessible.

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.4500 / 3.10.4504 / 3.11.2302 or later
Fixed in 3.10.45003.10.45043.11.2302
Interim mitigation

Apply vendor-supplied firmware patches when available; restrict web management interface access to trusted networks and implement URI filtering/monitoring to detect traversal attempts.

Recommended fix High confidence

MLNX OS: 3.10.4500, 3.11.2302, or 3.12.1002 (depending on branch); ONYX: 3.10.4504; MLNX GW: 8.1.4500 or 8.2.2300; NetRun Xc: 18.2.2200

  1. Identify the exact product and current version of the affected NVIDIA Mellanox device (MLNX OS, ONYX, MLNX GW, or NetRun Xc)
  2. For MLNX OS: If version is < 3.10.4500, upgrade to 3.10.4500 or higher; if version is >= 3.11.0000 and < 3.11.2302, upgrade to 3.11.2302 or higher; if version is < 3.12.1002, upgrade to 3.12.1002 or higher
  3. For ONYX: If version is < 3.10.4504, upgrade to 3.10.4504 or higher
  4. For MLNX GW: If version is < 8.1.4500, upgrade to 8.1.4500 or higher; if version is < 8.2.2300, upgrade to 8.2.2300 or higher
  5. For NetRun Xc: If version is < 18.2.2200, upgrade to 18.2.2200 or higher
  6. Obtain the firmware/software from NVIDIA's official support portal at nvidia.custhelp.com
  7. Follow NVIDIA's standard upgrade procedure for the specific device to apply the patched version
  8. Verify the upgrade was successful and the web interface is functioning correctly
Caveat Ensure compatibility with your specific hardware platform and review release notes for any behavioral changes before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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