gl-b3000_firmware: Improper Limitation of a Pathname to a Restricted Directory
CVE-2024-45262 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in gl-b3000_firmware from GL.iNet, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 4.5.19 as the first without the flaw, so updating gl-b3000_firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.67% chance of exploitation within 30 days, higher than 52% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update gl-b3000_firmware to 4.5.19 or a later version.
- Update gl-mt6000_firmware to 4.6.4 or a later version.
- Update gl-x300b_firmware to 4.5.18 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Gl-inet | gl-b3000_firmware | 4.5.18 up to, but not including, 4.5.19 | 4.5.19 |
| Gl-inet | gl-mt6000_firmware | 4.6.2 up to, but not including, 4.6.4 | 4.6.4 |
| Gl-inet | gl-x300b_firmware | 4.5.17 up to, but not including, 4.5.18 | 4.5.18 |
| Gl-inet | gl-xe300_firmware | 4.4.9 up to, but not including, 4.4.10; 4.3.17 up to, but not including, 4.3.18 | 4.4.10, 4.3.18 |
| Gl-inet | gl-x750_firmware | 4.3.18 up to, but not including, 4.3.19 | 4.3.19 |
| Gl-inet | Mt2500 Firmware | 4.6.2 up to, but not including, 4.6.4 | 4.6.4 |
| Gl-inet | Axt1800 Firmware | 4.6.2 up to, but not including, 4.6.4 | 4.6.4 |
| Gl-inet | Ax1800 Firmware | 4.6.2 up to, but not including, 4.6.4 | 4.6.4 |
| Gl-inet | B3000 Firmware | 4.5.18 | Not stated |
| Gl-inet | A1300 Firmware | 4.5.17 | Not stated |
| Gl-inet | X300b Firmware | 4.5.17 | Not stated |
| Gl-inet | X3000 Firmware | 4.4.9 | Not stated |
| Gl-inet | Xe3000 Firmware | 4.4.9 | Not stated |
| Gl-inet | X750 Firmware | 4.3.18 | Not stated |
| Gl-inet | Sft1200 Firmware | 4.3.18 | Not stated |
| Gl-inet | Mt1300 Firmware | 4.3.18 | Not stated |
| Gl-inet | E750 Firmware | 4.3.17 | Not stated |
| Gl-inet | Xe300 Firmware | 4.3.17 | Not stated |
| Gl-inet | Ar750 Firmware | 4.3.17 | Not stated |
| Gl-inet | Ar750s Firmware | 4.3.17 | Not stated |
| Gl-inet | Ar300m Firmware | 4.3.17 | Not stated |
| Gl-inet | Mt300n-v2 Firmware | 4.3.17 | Not stated |
| Gl-inet | Mt6000 Firmware | 4.6.2 | Not stated |
| Gl-inet | B1300 Firmware | 4.3.17 | Not stated |
| Gl-inet | Mt3000 Firmware | 4.6.2 | Not stated |
Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- 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
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
An issue was discovered on certain GL-iNet devices, including MT6000, MT3000, MT2500, AXT1800, and AX1800 4.6.2. The params parameter in the call method of the /rpc endpoint is vulnerable to arbitrary directory traversal, which enables attackers to execute scripts under any path.
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: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- github.com/gl-inet/CVE-issues/blob/main/4.0.0/Improper%20Pathname%20Restriction%20Leading%20to%20Path%20Trave…Exploit, Third Party Advisory
Other vulnerabilities in gl-b3000_firmware
- 8.8 High severity
- 8.0 High severity
- 8.0 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 8.0 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.