# CVE-2019-12412: Null dereference in libapreq2

> A remote attacker can cause a denial of service by triggering a null pointer dereference in the libapreq2 multipart parser.

- **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:** 18 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12412, DLA-1944-1, DSA-4541-1, GHSA-239h-283c-gxph, MGASA-2019-0327, UBUNTU-CVE-2019-12412, USN-4558-1, USN-5041-1

## What is CVE-2019-12412?

CVE-2019-12412 is a high-severity vulnerability in libapreq2, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw in the libapreq2 v2.07 to v2.13 multipart parser can deference a null pointer leading to a process crash. A remote attacker could send a request causing a process crash which could lead to a denial of service attack.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2019-12412?

It affects 1 product.


Products: Apache Libapreq2.

## How do I fix CVE-2019-12412?

Apply the vendor's patch.

## Is CVE-2019-12412 being exploited?

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

## Other vulnerabilities in libapreq2

- [CVE-2022-22728](https://insights.sbomify.com/CVE-2022-22728/): libapreq2 multipart form parse memory corruption (high 7.5)
- [CVE-2006-0042](https://insights.sbomify.com/CVE-2006-0042/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12412 and fix it if it is affected.

What it is: CVE-2019-12412 is a high-severity vulnerability in libapreq2, published on 18 Nov 2020. 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-2019-12412 in the wild and no public exploit code.

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

## Sources

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

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