# CVE-2024-10119: SECOM WRTM326 - OS Command Injection

> An unauthenticated remote attacker can execute arbitrary system commands on the SECOM WRTM326 wireless router due to improper parameter validation.

- **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:** 18 Oct 2024
- **Updated:** 18 Oct 2024
- **Also known as:** GHSA-3jvf-q93m-2fhw

## What is CVE-2024-10119?

CVE-2024-10119 is a critical command injection vulnerability in SECOM WRTM326, published on 18 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The wireless router WRTM326 from SECOM does not properly validate a specific parameter. An unauthenticated remote attacker could execute arbitrary system commands by sending crafted requests.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Zte Wrtm326 Firmware.

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

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

## Is CVE-2024-10119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10119 is a critical command injection vulnerability in SECOM WRTM326, published on 18 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10119 in the wild and no public exploit code.

Affected product: SECOM WRTM326. 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-10119/ (Markdown: https://insights.sbomify.com/CVE-2024-10119/index.md)
```

## Sources

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

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