Cyber Resilience

CVE-2024-39226

RCE in Gl-Inet Mt6000 Firmware 4.5.8

Published
06 August 2024
Modified
12 November 2024
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.21 97th percentile
Risk Priority 84 floored blend · peak EPSS

Summary

CVE-2024-39226 is a critical-severity Path Traversal (CWE-22) vulnerability in Gl-Inet Mt6000 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-39226 affects multiple GL-iNet router models running firmware versions including AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E750 v4.3.12, AP1300/S1300 v4.3.13, and XE3000/X3000 v4.4. The flaw is a command injection issue (with an associated path traversal component) in the s2s API that permits arbitrary shell command execution.

Unauthenticated remote attackers can supply crafted input to the s2s interface and thereby execute commands on the device. Successful exploitation grants full control over the router, allowing arbitrary code execution with impacts to confidentiality, integrity, and availability.

The single disclosed reference is a GitHub advisory that documents the s2s interface shell injection vector but does not detail patches or workarounds. The EPSS score has remained flat at 0.1364 with no material increase since publication.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GL-iNet products AR750/AR750S/AR300M/AR300M16/MT300N-V2/B1300/MT1300/SFT1200/X750 v4.3.11, MT3000/MT2500/AXT1800/AX1800/A1300/X300B v4.5.16, XE300 v4.3.16, E750 v4.3.12, AP1300/S1300 v4.3.13, and XE3000/X3000 v4.4 were discovered to contain a vulnerability can be exploited to manipulate routers by passing malicious shell commands through the s2s API.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-26791Same product: Gl-Inet Ar300M16
CVE-2026-26793Same product: Gl-Inet Ar300M16
CVE-2026-26795Same product: Gl-Inet Ar300M16
CVE-2026-26792Same product: Gl-Inet Ar300M16
CVE-2023-31473Same vendor: Gl-Inet
CVE-2023-31476Same vendor: Gl-Inet
CVE-2025-67089Same vendor: Gl-Inet
CVE-2023-50445Same vendor: Gl-Inet
CVE-2023-47464Same vendor: Gl-Inet
CVE-2023-31477Same vendor: Gl-Inet

Affected Assets

gl-inet
mt6000 firmware
4.5.8
gl-inet
a1300 firmware
4.5.16
gl-inet
x300b firmware
4.5.16
gl-inet
ax1800 firmware
4.5.16
gl-inet
axt1800 firmware
4.5.16
gl-inet
mt2500 firmware
4.5.16
gl-inet
mt3000 firmware
4.5.16
gl-inet
x3000 firmware
4.4.8
gl-inet
xe3000 firmware
4.4.8
gl-inet
xe300 firmware
4.3.16
+18 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

mitigates

Information access restriction limits which files an application may read or write.

References