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

> Unauthenticated attackers can execute arbitrary code or perform directory traversal on GL-iNet routers via crafted JSON data in the /cgi-bin/glc endpoint.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2024
- **Updated:** 15 Aug 2024
- **Also known as:** GHSA-8j3m-968h-m85q

## What is CVE-2024-39227?

CVE-2024-39227 is a critical command injection vulnerability in n/a, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, 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 insecure permissions in the endpoint /cgi-bin/glc. This vulnerability allows unauthenticated attackers to execute arbitrary code or possibly a directory traversal via crafted JSON data.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

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

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-39227?

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

## Is CVE-2024-39227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39227 exists.

## Other vulnerabilities in n/a

- [CVE-2024-39225](https://insights.sbomify.com/CVE-2024-39225/): Other 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)
- [CVE-2024-45260](https://insights.sbomify.com/CVE-2024-45260/): Missing authorization in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39227 is a critical command injection vulnerability in n/a, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39227 exists.

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-39227/ (Markdown: https://insights.sbomify.com/CVE-2024-39227/index.md)
```

## Sources

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

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