# CVE-2024-52321: Information disclosure in PocketWifi 809SH

> Remote unauthenticated attackers can retrieve sensitive configuration backup files from multiple SHARP mobile routers.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 23 Dec 2024
- **Updated:** 24 Dec 2024
- **Also known as:** GHSA-33wm-fghj-g69f

## What is CVE-2024-52321?

CVE-2024-52321 is a medium-severity vulnerability in Sharp Corporation PocketWifi 809SH, published on 23 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SHARP routers contain an improper authentication vulnerability in the configuration backup function. The product's backup files containing sensitive information may be retrieved by a remote unauthenticated attacker.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2024-52321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52321 is a medium-severity vulnerability in Sharp Corporation PocketWifi 809SH, published on 23 Dec 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-52321 in the wild and no public exploit code.

Affected product: Sharp Corporation PocketWifi 809SH. 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-52321/ (Markdown: https://insights.sbomify.com/CVE-2024-52321/index.md)
```

## Sources

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

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