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

> A stack buffer overflow in Libraw allows attackers to execute arbitrary code or cause denial of service via crafted DNG files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-24870, GHSA-p736-65cp-9pj8, UBUNTU-CVE-2020-24870

## What is CVE-2020-24870?

CVE-2020-24870 is a high-severity memory corruption vulnerability in Libraw Libraw, published on 2 Jun 2021. 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

Libraw before 0.20.1 has a stack buffer overflow via LibRaw::identify_process_dng_fields in identify.cpp.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Libraw Libraw.

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

Upgrade to a fixed version.

## Is CVE-2020-24870 being exploited?

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

## 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-24870 and fix it if it is affected.

What it is: CVE-2020-24870 is a high-severity memory corruption vulnerability in Libraw Libraw, published on 2 Jun 2021. 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-2020-24870 in the wild and no public exploit code.

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

## Sources

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

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