# CVE-2022-22728: libapreq2 multipart form parse memory corruption

> A buffer overflow in Apache libapreq2 allows remote attackers to cause a denial of service via crafted multipart form uploads.

- **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:** 25 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-22728, DLA-3269-1, GHSA-jq3x-hcjw-4j6x, MGASA-2023-0123, UBUNTU-CVE-2022-22728

## What is CVE-2022-22728?

CVE-2022-22728 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 25 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw in Apache libapreq2 versions 2.16 and earlier could cause a buffer overflow while processing multipart form uploads. A remote attacker could send a request causing a process crash which could lead to a denial of service attack.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-22728?

It affects 3 products.


Products: Apache Libapreq2, Debian Debian Linux, Fedoraproject Fedora.

## How do I fix CVE-2022-22728?

Apply the vendor's patch.

## Is CVE-2022-22728 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2019-12412](https://insights.sbomify.com/CVE-2019-12412/): Null dereference in libapreq2 (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-2022-22728 and fix it if it is affected.

What it is: CVE-2022-22728 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 25 Aug 2022. 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-2022-22728 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2022-22728/ (Markdown: https://insights.sbomify.com/CVE-2022-22728/index.md)
```

## Sources

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

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