# CVE-2024-11983: Billion Electric router - OS Command Injection

> Remote attackers with admin privileges can inject arbitrary system commands into SSH functions on Billion Electric routers, leading to code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2024
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-88vw-p4cx-4677

## What is CVE-2024-11983?

CVE-2024-11983 is a high-severity command injection vulnerability in Billion Electric M100, published on 29 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Certain models of routers from Billion Electric has an OS Command Injection vulnerability, allowing remote attackers with administrator privileges to inject arbitrary system commands into a specific SSH function and execute them on the device.

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

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


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

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

## Is CVE-2024-11983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11983 is a high-severity command injection vulnerability in Billion Electric M100, published on 29 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11983 in the wild and no public exploit code.

Affected product: Billion Electric M100. 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-11983/ (Markdown: https://insights.sbomify.com/CVE-2024-11983/index.md)
```

## Sources

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

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