# CVE-2022-31796: Memory corruption in n/a

> A heap-based buffer over-read in libjpeg allows attackers to cause denial of service or disclose sensitive memory contents via crafted images.

- **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:** 29 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-31796, GHSA-hxpg-2x22-5xr4, UBUNTU-CVE-2022-31796

## What is CVE-2022-31796?

CVE-2022-31796 is a medium-severity memory corruption vulnerability in n/a, published on 29 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

libjpeg 1.63 has a heap-based buffer over-read in HierarchicalBitmapRequester::FetchRegion in hierarchicalbitmaprequester.cpp because the MCU size can be different between allocation and use.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Jpeg Libjpeg.

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

Upgrade to a fixed version.

## Is CVE-2022-31796 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37768](https://insights.sbomify.com/CVE-2022-37768/): Denial of service in n/a (high 7.5)
- [CVE-2023-37836](https://insights.sbomify.com/CVE-2023-37836/): Denial of service in n/a (medium 6.5)
- [CVE-2023-37837](https://insights.sbomify.com/CVE-2023-37837/): Memory corruption in n/a (medium 6.5)
- [CVE-2022-37769](https://insights.sbomify.com/CVE-2022-37769/): Denial of service in n/a (medium 6.5)
- [CVE-2022-37770](https://insights.sbomify.com/CVE-2022-37770/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31796 is a medium-severity memory corruption vulnerability in n/a, published on 29 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-31796 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-31796/ (Markdown: https://insights.sbomify.com/CVE-2022-31796/index.md)
```

## Sources

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

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