# CVE-2024-41311: Memory corruption in n/a

> An attacker can trigger out-of-bounds read and write via a crafted HEIF file, potentially leading to code execution or denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **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:** 15 Oct 2024
- **Updated:** 23 Oct 2024
- **Also known as:** DEBIAN-CVE-2024-41311, DLA-3934-1, GHSA-mwf7-wfvq-vc32, MGASA-2024-0352, SUSE-SU-2024:3960-1, UBUNTU-CVE-2024-41311, USN-7082-1

## What is CVE-2024-41311?

CVE-2024-41311 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 15 Oct 2024. 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 Libheif 1.17.6, insufficient checks in ImageOverlay::parse() decoding a heif file containing an overlay image with forged offsets can lead to an out-of-bounds read and write.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-41311?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libheif` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 1.12.0-150400.3.14.1 |
| `libheif` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 1.12.0-150400.3.14.1 |
| `libheif` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 1.12.0-150400.3.14.1 |
| `libheif` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 1.12.0-150400.3.14.1 |
| `libheif` | openSUSE:Leap 15.5 | All versions | 1.12.0-150400.3.14.1 |
| `libheif` | openSUSE:Leap 15.6 | All versions | 1.12.0-150400.3.14.1 |

Products: Debian Debian Linux, Struktur Libheif.

## How do I fix CVE-2024-41311?

Upgrade to a fixed version.

## Is CVE-2024-41311 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41311 and fix it if it is affected.

What it is: CVE-2024-41311 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 15 Oct 2024. 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-2024-41311 exists.

Affected product: Debian Debian Linux. 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-2024-41311/ (Markdown: https://insights.sbomify.com/CVE-2024-41311/index.md)
```

## Sources

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

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