M11sdv-4c-ln4f Firmware: Improper Limitation of a Pathname to a Restricted Directory
CVE-2023-33411 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in M11sdv-4c-ln4f Firmware from Supermicro, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected M11sdv-4c-ln4f Firmware versions: 3.17.02 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.28% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of M11sdv-4c-ln4f Firmware you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on supermicro.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.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Supermicro | M11sdv-4c-ln4f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | M11sdv-4ct-ln4f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | M11sdv-8c-ln4f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | M11sdv-8ct-ln4f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-pg Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-pg300 Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-pg300f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-pgf Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-pgf-l Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-rpgf Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | C9x299-rpgf-l Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | B13dee Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | B13det Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | B13see-cpu-25g Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | B13seg Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13dsg-o-cpu Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13dsg-o-cpu-d Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13dsg-om Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13dsh Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13sae-mf Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13sra-f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13sra-tf Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13srd-f Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13ssf Firmware | 3.17.02 and earlier | Not stated |
| Supermicro | H13ssh Firmware | 3.17.02 and earlier | Not stated |
Version data comes from NVD's product matching; 35 further products are omitted here. 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
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
Official description
A web server in the Intelligent Platform Management Interface (IPMI) baseboard management controller (BMC) implementation on Supermicro X11 and M11 based devices, with firmware versions up to 3.17.02, allows remote unauthenticated users to perform directory traversal, potentially disclosing sensitive information.
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: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in M11sdv-4c-ln4f Firmware
- 8.8 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.