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

> A NULL pointer dereference in libming allows attackers to cause a denial of service via crafted input.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-75g3-c2w4-6cxv, UBUNTU-CVE-2018-20429

## What is CVE-2018-20429?

CVE-2018-20429 is a high-severity vulnerability in Libming Libming, published on 24 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

libming 0.4.8 has a NULL pointer dereference in the getName function of the decompile.c file, a different vulnerability than CVE-2018-7872 and CVE-2018-9165.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Libming Libming.

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

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

## Is CVE-2018-20429 being exploited?

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

## Other vulnerabilities in Libming Libming

- [CVE-2023-50628](https://insights.sbomify.com/CVE-2023-50628/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11894](https://insights.sbomify.com/CVE-2020-11894/): Memory corruption in n/a (critical 9.1)
- [CVE-2020-11895](https://insights.sbomify.com/CVE-2020-11895/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-16705](https://insights.sbomify.com/CVE-2019-16705/): Information disclosure in n/a (critical 9.1)
- [CVE-2023-36239](https://insights.sbomify.com/CVE-2023-36239/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20429 is a high-severity vulnerability in Libming Libming, published on 24 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-20429 in the wild and no public exploit code.

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

## Sources

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

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