# CVE-2022-31620: Denial of service in n/a

> An out-of-bounds array access in libjpeg can cause an assertion failure and denial of service when processing specific JPEG scans.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-31620, GHSA-62v2-wx44-h68c, UBUNTU-CVE-2022-31620

## What is CVE-2022-31620?

CVE-2022-31620 is a medium-severity denial of service vulnerability in n/a, published on 25 May 2022. 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

In libjpeg before 1.64, BitStream<false>::Get in bitstream.hpp has an assertion failure that may cause denial of service. This is related to out-of-bounds array access during arithmetically coded lossless scan or arithmetically coded sequential scan.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


Products: Libjpeg Project Libjpeg.

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

Upgrade to a fixed version.

## Is CVE-2022-31620 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32201](https://insights.sbomify.com/CVE-2022-32201/): Null dereference in n/a (medium 5.5)
- [CVE-2022-32202](https://insights.sbomify.com/CVE-2022-32202/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31620 is a medium-severity denial of service vulnerability in n/a, published on 25 May 2022. 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-2022-31620 in the wild and no public exploit code.

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

## Sources

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

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