# CVE-2024-48895: Command injection in Rakuten Turbo 5G

> Remote authenticated attackers can execute arbitrary OS commands on Rakuten Turbo 5G devices due to improper input neutralization.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-cgpm-vvq7-c2vr

## What is CVE-2024-48895?

CVE-2024-48895 is a high-severity command injection vulnerability in Rakuten Turbo 5G, published on 20 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in Rakuten Turbo 5G firmware version V1.3.18 and earlier. If this vulnerability is exploited, a remote authenticated attacker may execute an arbitrary OS command.

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

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


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

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

## Is CVE-2024-48895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48895 is a high-severity command injection vulnerability in Rakuten Turbo 5G, published on 20 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48895 in the wild and no public exploit code.

Affected product: Rakuten Turbo 5G. 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-48895/ (Markdown: https://insights.sbomify.com/CVE-2024-48895/index.md)
```

## Sources

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

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