# CVE-2024-6199: Unauthenticated Remote Code Execution

> An attacker can achieve remote code execution on ViaSat modems by exploiting a buffer overflow via manipulated Dynamic DNS traffic if DDNS is enabled.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N/AU:N/R:U/V:D/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:** 25 Apr 2025
- **Also known as:** GHSA-854w-ph8g-6mrh

## What is CVE-2024-6199?

CVE-2024-6199 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

An unauthenticated attacker on the WAN interface, with the ability to intercept Dynamic DNS (DDNS) traffic between DDNS services and the modem, could manipulate specific responses to include code that forces a buffer overflow on the modem.

Customers that have not enabled Dynamic DNS on their modem are not vulnerable.

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

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


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

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

## Is CVE-2024-6199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6199 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-6199 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-6199/ (Markdown: https://insights.sbomify.com/CVE-2024-6199/index.md)
```

## Sources

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

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