# CVE-2018-1000052: Memory corruption in n/a

> An attacker can cause a denial of service via memory corruption in fmtlib by specifying an invalid format specifier in the print function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000052, GHSA-w83v-wch9-fjvr, UBUNTU-CVE-2018-1000052

## What is CVE-2018-1000052?

CVE-2018-1000052 is a high-severity memory corruption vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fmtlib version prior to version 4.1.0 (before commit 0555cea5fc0bf890afe0071a558e44625a34ba85) contains a Memory corruption (SIGSEGV), CWE-134 vulnerability in fmt::print() library function that can result in Denial of Service. This attack appear to be exploitable via Specifying an invalid format specifier in the fmt::print() function results in a SIGSEGV (memory corruption, invalid write). This vulnerability appears to have been fixed in after commit 8cf30aa2be256eba07bb1cefb998c52326e846e7.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2018-1000052?

It affects 1 product.


Products: Fmt Fmt.

## How do I fix CVE-2018-1000052?

Upgrade to a fixed version.

## Is CVE-2018-1000052 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000052 and fix it if it is affected.

What it is: CVE-2018-1000052 is a high-severity memory corruption vulnerability in n/a, published on 9 Feb 2018. 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-2018-1000052 in the wild and no public exploit code.

Affected product: n/a. 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-2018-1000052/ (Markdown: https://insights.sbomify.com/CVE-2018-1000052/index.md)
```

## Sources

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

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