# CVE-2022-28653: Denial of service in Apport

> Attackers can exhaust disk space in /var/crash via Apport, causing denial of service on Ubuntu systems.

- **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:** No
- **Published:** 31 Jan 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-5jgw-fw55-g7x3, UBUNTU-CVE-2022-28653

## What is CVE-2022-28653?

CVE-2022-28653 is a high-severity denial of service vulnerability in Canonical Ltd. Apport, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Users can consume unlimited disk space in /var/crash

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

It affects 1 product.


Products: Canonical Apport.

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

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

## Is CVE-2022-28653 being exploited?

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

## Other vulnerabilities in Canonical Ltd. Apport

- [CVE-2021-25682](https://insights.sbomify.com/CVE-2021-25682/): apport improperly parses /proc/pid/status (high 8.8)
- [CVE-2021-25683](https://insights.sbomify.com/CVE-2021-25683/): apport improperly parses /proc/pid/stat (high 8.8)
- [CVE-2021-25684](https://insights.sbomify.com/CVE-2021-25684/): apport can be stalled by reading a FIFO (high 8.8)
- [CVE-2021-3899](https://insights.sbomify.com/CVE-2021-3899/): Race condition in Apport (high 7.8)
- [CVE-2022-1242](https://insights.sbomify.com/CVE-2022-1242/): Other in Apport (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28653 and fix it if it is affected.

What it is: CVE-2022-28653 is a high-severity denial of service vulnerability in Canonical Ltd. Apport, published on 31 Jan 2025. 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-28653 in the wild and no public exploit code.

Affected product: Canonical Ltd. Apport. 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-28653/ (Markdown: https://insights.sbomify.com/CVE-2022-28653/index.md)
```

## Sources

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

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