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

> Attackers can execute arbitrary commands on Motorola CX2L routers via the SetStationSettings function due to lack of input filtering.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2024
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-wq2q-69wh-j8r2

## What is CVE-2024-45880?

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

### Official description

A command injection vulnerability exists in Motorola CX2L router v1.0.2 and below. The vulnerability is present in the SetStationSettings function. The system directly invokes the system function to execute commands for setting parameters such as MAC address without proper input filtering. This allows malicious users to inject and execute arbitrary commands.

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

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


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

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

## Is CVE-2024-45880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45880 is a high-severity command injection vulnerability in n/a, published on 8 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45880 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-45880/ (Markdown: https://insights.sbomify.com/CVE-2024-45880/index.md)
```

## Sources

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

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