# CVE-2024-48871: Planet Technology Planet WGS-804HPT Stack-based Buffer Overflow

> An unauthenticated attacker can achieve remote code execution via a stack-based buffer overflow in the web server of Planet Technology switches.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2024
- **Updated:** 6 Dec 2024
- **Also known as:** GHSA-jpgm-g5cc-54qg

## What is CVE-2024-48871?

CVE-2024-48871 is a critical memory corruption vulnerability in Planet WGS-804HPT, published on 6 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected product is vulnerable to a stack-based buffer overflow. An unauthenticated attacker could send a malicious HTTP request that the webserver fails to properly check input size before copying data to the stack, potentially allowing remote code execution.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2024-48871 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48871 is a critical memory corruption vulnerability in Planet WGS-804HPT, published on 6 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-48871 in the wild and no public exploit code.

Affected product: Planet WGS-804HPT. 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-48871/ (Markdown: https://insights.sbomify.com/CVE-2024-48871/index.md)
```

## Sources

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

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