# CVE-2024-45721: Command injection in Wi-Fi STATION SH-52B

> Administrative users can execute arbitrary OS commands with root privileges via the HOST name configuration screen in Sharp 5G Wi-Fi stations.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 23 Dec 2024
- **Updated:** 24 Dec 2024
- **Also known as:** GHSA-xpmr-c35p-q4rw

## What is CVE-2024-45721?

CVE-2024-45721 is a high-severity command injection vulnerability in Sharp Corporation Wi-Fi STATION SH-52B, published on 23 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

home 5G HR02, Wi-Fi STATION SH-52B, and Wi-Fi STATION SH-54C contain an OS command injection vulnerability in the HOST name configuration screen. An arbitrary OS command may be executed with the root privilege by an administrative user.

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

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


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

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

## Is CVE-2024-45721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45721 is a high-severity command injection vulnerability in Sharp Corporation Wi-Fi STATION SH-52B, published on 23 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45721 in the wild and no public exploit code.

Affected product: Sharp Corporation Wi-Fi STATION SH-52B. 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-45721/ (Markdown: https://insights.sbomify.com/CVE-2024-45721/index.md)
```

## Sources

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

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