# CVE-2024-47865: Missing authorization in Rakuten Turbo 5G

> Remote attackers can update or downgrade firmware on Rakuten Turbo 5G devices due to missing authentication for critical functions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-62m8-j435-v728

## What is CVE-2024-47865?

CVE-2024-47865 is a medium-severity missing authorization vulnerability in Rakuten Turbo 5G, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing authentication for critical function vulnerability exists in Rakuten Turbo 5G firmware version V1.3.18 and earlier. If this vulnerability is exploited, a remote unauthenticated attacker may update or downgrade the firmware on the device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2024-47865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47865 is a medium-severity missing authorization vulnerability in Rakuten Turbo 5G, published on 20 Nov 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-47865 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-47865/ (Markdown: https://insights.sbomify.com/CVE-2024-47865/index.md)
```

## Sources

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

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