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

> Attackers can cause a denial of service via a crafted file due to a segmentation fault in the libjpeg library.

- **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:** 18 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-37770, GHSA-7v22-7rx4-h6f8, UBUNTU-CVE-2022-37770

## What is CVE-2022-37770?

CVE-2022-37770 is a medium-severity denial of service vulnerability in n/a, published on 18 Aug 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 commit 281daa9 was discovered to contain a segmentation fault via LineMerger::GetNextLowpassLine at linemerger.cpp. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Jpeg Libjpeg.

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

Apply the vendor's patch.

## Is CVE-2022-37770 being exploited?

There is no known exploitation of CVE-2022-37770 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-32978](https://insights.sbomify.com/CVE-2022-32978/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37770 is a medium-severity denial of service vulnerability in n/a, published on 18 Aug 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-37770 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-37770/ (Markdown: https://insights.sbomify.com/CVE-2022-37770/index.md)
```

## Sources

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

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