# CVE-2018-1000101: Null dereference in n/a

> An improper null termination flaw in the MinGW-w64 C runtime library can lead to memory corruption, potentially allowing code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 6 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000101, GHSA-2994-cf23-4hmp, UBUNTU-CVE-2018-1000101

## What is CVE-2018-1000101?

CVE-2018-1000101 is a critical vulnerability in n/a, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mingw-w64 version 5.0.3 and earlier, 5.0.4, 6.0.0 and 7.0.0 contains an Improper Null Termination (CWE-170) vulnerability in mingw-w64-crt (libc)->(v)snprintf that can result in The bug may be used to corrupt subsequent string functions. This attack appear to be exploitable via Depending on the usage, worst case: network.

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

It affects 1 product.


Products: Mingw-W64 Mingw-W64.

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

Upgrade to a fixed version.

## Is CVE-2018-1000101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000101 is a critical vulnerability in n/a, published on 6 Mar 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-1000101 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-1000101/ (Markdown: https://insights.sbomify.com/CVE-2018-1000101/index.md)
```

## Sources

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

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