# CVE-2024-6198: SNORE Interface Unauthenticated Remote Code Execution

> An attacker on the local network can execute arbitrary code on ViaSat modems via a stack buffer overflow in the SNORE web interface.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N/AU:Y/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qc4v-92xf-xp3m

## What is CVE-2024-6198?

CVE-2024-6198 is a high-severity memory corruption vulnerability in ViaSat EG1000, published on 25 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The device exposes a web interface on ports TCP/3030 and TCP/9882. This web service runs lighttpd, which implements the “SNORE” interface. This interface is affected by a stack buffer overflow vulnerability due to insecure path parsing. An attacker
with access to the LAN network interface could use a specially crafted HTTP request to exploit a buffer overflow on the modem.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2024-6198 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6198 is a high-severity memory corruption vulnerability in ViaSat EG1000, published on 25 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6198 in the wild and no public exploit code.

Affected product: ViaSat EG1000. 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-6198/ (Markdown: https://insights.sbomify.com/CVE-2024-6198/index.md)
```

## Sources

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

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