# CVE-2023-26552: Memory corruption in n/a

> An out-of-bounds write in the NTP client utility allows attackers to potentially execute code or cause denial of service via crafted input.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-26552, GHSA-55jm-6fgm-6r95, UBUNTU-CVE-2023-26552

## What is CVE-2023-26552?

CVE-2023-26552 is a medium-severity memory corruption vulnerability in Ntp Ntp, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mstolfp in libntp/mstolfp.c in NTP 4.2.8p15 has an out-of-bounds write when adding a decimal point. An adversary may be able to attack a client ntpq process, but cannot attack ntpd.

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

## Which versions are affected by CVE-2023-26552?

It affects 1 product.


Products: Ntp Ntp.

## How do I fix CVE-2023-26552?

Apply the vendor's patch.

## Is CVE-2023-26552 being exploited?

There is no known exploitation of CVE-2023-26552 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-6451](https://insights.sbomify.com/CVE-2017-6451/): Memory corruption in n/a (high 7.8)
- [CVE-2017-6452](https://insights.sbomify.com/CVE-2017-6452/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26552 and fix it if it is affected.

What it is: CVE-2023-26552 is a medium-severity memory corruption vulnerability in Ntp Ntp, published on 11 Apr 2023. 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-2023-26552 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-2023-26552/ (Markdown: https://insights.sbomify.com/CVE-2023-26552/index.md)
```

## Sources

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

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