# CVE-2017-6451: Memory corruption in n/a

> Local attackers can execute arbitrary code via an out-of-bounds memory write in the NTP MX4200 refclock driver.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mg4x-c4g8-f6h5

## What is CVE-2017-6451?

CVE-2017-6451 is a high-severity memory corruption vulnerability in Ntp Ntp, published on 27 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The mx4200_send function in the legacy MX4200 refclock in NTP before 4.2.8p10 and 4.3.x before 4.3.94 does not properly handle the return value of the snprintf function, which allows local users to execute arbitrary code via unspecified vectors, which trigger an out-of-bounds memory write.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-6451?

It affects 1 product.


Products: Ntp Ntp.

## How do I fix CVE-2017-6451?

Upgrade to a fixed version.

## Is CVE-2017-6451 being exploited?

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

## Other vulnerabilities in Ntp Ntp

- [CVE-2018-12327](https://insights.sbomify.com/CVE-2018-12327/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6460](https://insights.sbomify.com/CVE-2017-6460/): Memory corruption in n/a (high 8.8)
- [CVE-2019-11331](https://insights.sbomify.com/CVE-2019-11331/): Other in n/a (high 8.1)
- [CVE-2017-6452](https://insights.sbomify.com/CVE-2017-6452/): Memory corruption in n/a (high 7.8)
- [CVE-2017-6462](https://insights.sbomify.com/CVE-2017-6462/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6451 and fix it if it is affected.

What it is: CVE-2017-6451 is a high-severity memory corruption vulnerability in Ntp Ntp, published on 27 Mar 2017. 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-2017-6451 in the wild and no public exploit code.

Affected product: Ntp Ntp. 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-2017-6451/ (Markdown: https://insights.sbomify.com/CVE-2017-6451/index.md)
```

## Sources

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

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