# CVE-2022-1922: Integer overflow in GStreamer

> An integer overflow in GStreamer's Matroska demuxer can cause a crash or heap overwrite, potentially leading to denial of service or code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** CLEANSTART-2026-VZ54058, DEBIAN-CVE-2022-1922, GHSA-2cxw-4p8f-4qp7, UBUNTU-CVE-2022-1922

## What is CVE-2022-1922?

CVE-2022-1922 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

DOS / potential heap overwrite in mkv demuxing using zlib decompression. Integer overflow in matroskademux element in gst_matroska_decompress_data function which causes a segfault, or could cause a heap overwrite, depending on libc and OS. Depending on the libc used, and the underlying OS capabilities, it could be just a segfault or a heap overwrite. If the libc uses mmap for large chunks, and the OS supports mmap, then it is just a segfault (because the realloc before the integer overflow will use mremap to reduce the size of the chunk, and it will start to write to unmapped memory). However, if using a libc implementation that does not use mmap, or if the OS does not support mmap while using libc, then this could result in a heap overwrite.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

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

It affects 2 products.


Products: Debian Debian Linux, Gstreamer Gstreamer.

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

Apply the vendor's patch.

## Is CVE-2022-1922 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1922 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1922 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-1922/ (Markdown: https://insights.sbomify.com/CVE-2022-1922/index.md)
```

## Sources

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

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