# CVE-2024-39226: Command injection in n/a

> Attackers can execute arbitrary shell commands on GL-iNet routers via the s2s API, potentially compromising the device.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-9qmq-f7gc-gf44

## What is CVE-2024-39226?

CVE-2024-39226 is a medium-severity command injection vulnerability in n/a, published on 6 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-39226?

It affects 28 products.


Products: Gl-Inet A1300 Firmware, Gl-Inet Ap1300 Firmware, Gl-Inet Ar300m16 Firmware, Gl-Inet Ar300m Firmware, Gl-Inet Ar750 Firmware, Gl-Inet Ar750s Firmware, Gl-Inet Ax1800 Firmware, Gl-Inet Axt1800 Firmware, Gl-Inet B1300 Firmware, Gl-Inet B2200 Firmware, Gl-Inet E750 Firmware, Gl-Inet Mt1300 Firmware, Gl-Inet Mt2500 Firmware, Gl-Inet Mt3000 Firmware, Gl-Inet Mt300n-V2 Firmware, Gl-Inet Mt6000 Firmware, Gl-Inet Mv1000 Firmware, Gl-Inet Mv1000w Firmware, Gl-Inet N300 Firmware, Gl-Inet S1300 Firmware and 8 more.

## How do I fix CVE-2024-39226?

No fix has been published for CVE-2024-39226 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-39226 being exploited?

There is no known exploitation of CVE-2024-39226 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-39225](https://insights.sbomify.com/CVE-2024-39225/): Other in n/a (critical 9.8)
- [CVE-2024-39227](https://insights.sbomify.com/CVE-2024-39227/): Command injection in n/a (critical 9.8)
- [CVE-2024-39228](https://insights.sbomify.com/CVE-2024-39228/): Command injection in n/a (critical 9.8)
- [CVE-2024-45262](https://insights.sbomify.com/CVE-2024-45262/): Path traversal in n/a (high 8.8)
- [CVE-2024-45263](https://insights.sbomify.com/CVE-2024-45263/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39226 and fix it if it is affected.

What it is: CVE-2024-39226 is a medium-severity command injection vulnerability in n/a, published on 6 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-39226 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-39226/ (Markdown: https://insights.sbomify.com/CVE-2024-39226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39226
- OSV: https://osv.dev/vulnerability/CVE-2024-39226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-39226/
Summaries are generated and may contain mistakes; the official description above is the record.