Mellanox OS: Improper Limitation of a Pathname to a Restricted Directory
CVE-2024-0113 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Mellanox OS from NVIDIA, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Mellanox OS versions: All versions prior to and including 3.11.4000; All versions prior to and including 3.11.2200; All versions prior to and including 3.10.4400. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.09% chance of exploitation within 30 days, higher than 66% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Mlnx-os to 3.10.4500 or 3.12.1002 or 3.11.2302, whichever matches your release line, or a later version.
- Update Onyx to 3.10.4504 or a later version.
- Update Mlnx-gw to 8.1.4500 or 8.2.2300, whichever matches your release line, or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | Mellanox OS | All versions prior to and including 3.11.4000; All versions prior to and including 3.11.2200; All versions prior to and including 3.10.4400 | Not stated |
| NVIDIA | Skyway | All versions prior to and including 8.2.2200; All versions prior to and including 8.1.4400 | Not stated |
| NVIDIA | MetroX-3 XC | All versions prior to and including 18.2.2200 | Not stated |
| NVIDIA | MetroX-2 | All versions prior to and including 3.11.4000 | Not stated |
| NVIDIA | mellanox_os_firmware | 3.11.4000 and earlier; 3.11.2200 and earlier; 3.10.4400 and earlier | Not stated |
| NVIDIA | skyway_firmware | 8.2.2200 and earlier; 8.1.4400 and earlier | Not stated |
| NVIDIA | metrox-2_firmware | 3.11.4000 and earlier | Not stated |
| NVIDIA | metrox-3_xc_firmware | 18.2.2200 and earlier | Not stated |
| NVIDIA | Mlnx-os | before 3.10.4500; before 3.12.1002; 3.11.0000 up to, but not including, 3.11.2302 | 3.10.4500, 3.12.1002, 3.11.2302 |
| NVIDIA | Onyx | before 3.10.4504 | 3.10.4504 |
| NVIDIA | Mlnx-gw | before 8.1.4500; before 8.2.2300 | 8.1.4500, 8.2.2300 |
| NVIDIA | Nvda-os Xc | before 18.2.2200 | 18.2.2200 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (nvidia.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Mellanox OS
- 8.8 High severity
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.