# CVE-2020-22628: Memory corruption in n/a

> A buffer overflow in LibRaw's aspect ratio processing allows attackers to execute arbitrary code or cause denial of service 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:** 22 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** DEBIAN-CVE-2020-22628, DLA-3560-1, GHSA-c4mp-wp8f-qrg6, SUSE-SU-2023:3966-1, SUSE-SU-2023:3967-1, SUSE-SU-2023:3968-1, UBUNTU-CVE-2020-22628, USN-6377-1, openSUSE-SU-2024:13252-1

## What is CVE-2020-22628?

CVE-2020-22628 is a medium-severity memory corruption vulnerability in Libraw Libraw, published on 22 Aug 2023. 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

Buffer Overflow vulnerability in LibRaw::stretch() function in libraw\src\postprocessing\aspect_ratio.cpp.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-22628?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libraw` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.15.4-42.1 |
| `libraw` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 0.15.4-42.1 |
| `libraw` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 0.18.9-150000.3.23.1 |
| `libraw` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | SUSE:Linux Enterprise Workstation Extension 15 SP5 | All versions | 0.18.9-150000.3.23.1 |
| `libraw` | SUSE:Linux Enterprise Workstation Extension 15 SP5 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | openSUSE:Leap 15.4 | All versions | 0.18.9-150000.3.23.1 |
| `libraw` | openSUSE:Leap 15.4 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | openSUSE:Leap 15.5 | All versions | 0.20.2-150400.3.9.1 |
| `libraw` | openSUSE:Tumbleweed | All versions | 0.21.1-3.1 |

Products: Libraw Libraw.

## How do I fix CVE-2020-22628?

Apply the vendor's patch.

## Is CVE-2020-22628 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-22628 exists.

## Other vulnerabilities in Libraw Libraw

- [CVE-2026-20889](https://insights.sbomify.com/CVE-2026-20889/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2026-20911](https://insights.sbomify.com/CVE-2026-20911/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2026-21413](https://insights.sbomify.com/CVE-2026-21413/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2015-8366](https://insights.sbomify.com/CVE-2015-8366/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-8367](https://insights.sbomify.com/CVE-2015-8367/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-22628 and fix it if it is affected.

What it is: CVE-2020-22628 is a medium-severity memory corruption vulnerability in Libraw Libraw, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-22628 exists.

Affected product: Libraw Libraw. 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-2020-22628/ (Markdown: https://insights.sbomify.com/CVE-2020-22628/index.md)
```

## Sources

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

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