# CVE-2024-32035: Memory Allocation with Excessive Size Value in SixLabors.ImageSharp > Attackers can cause denial of service by exhausting memory via specially crafted image files processed by the ImageSharp library. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Apr 2024 - **Updated:** 2 Aug 2024 - **Also known as:** ECHO-208b-d6b3-dfb9, GHSA-g85r-6x2q-45w7 ## What is CVE-2024-32035? CVE-2024-32035 is a medium-severity denial of service vulnerability in SixLabors ImageSharp, published on 15 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ImageSharp is a 2D graphics API. A vulnerability discovered in the ImageSharp library, where the processing of specially crafted files can lead to excessive memory usage in image decoders. The vulnerability is triggered when ImageSharp attempts to process image files that are designed to exploit this flaw. This flaw can be exploited to cause a denial of service (DoS) by depleting process memory, thereby affecting applications and services that rely on ImageSharp for image processing tasks. Users and administrators are advised to update to the latest version of ImageSharp that addresses this vulnerability to mitigate the risk of exploitation. The problem has been patched in v3.1.4 and v2.1.8. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-789 (Memory Allocation with Excessive Size Value) ## Which versions are affected by CVE-2024-32035? 4 open source packages ship an affected version, including SixLabors.ImageSharp. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `SixLabors.ImageSharp` | NuGet | All versions | 2.1.8 | | `SixLabors.ImageSharp` | NuGet | All versions | 2.1.8 | | `SixLabors.ImageSharp` | NuGet | From 3.0.0 | 3.1.4 | | `SixLabors.ImageSharp` | NuGet | From 3.0.0 | 3.1.4 | Products: Sixlabors Imagesharp. ## How do I fix CVE-2024-32035? Upgrade SixLabors.ImageSharp to a fixed version for your release line: 2.1.8 or 3.1.4. ## Is CVE-2024-32035 being exploited? There is no known exploitation of CVE-2024-32035 in the wild and no public exploit code. ## Other vulnerabilities in SixLabors ImageSharp - [CVE-2026-106110](https://insights.sbomify.com/CVE-2026-106110/): ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer (high 7.5) - [CVE-2026-106112](https://insights.sbomify.com/CVE-2026-106112/): ImageSharp: ICC LUT16 output channel count can write beyond Vector4 (high 7.5) - [CVE-2026-106113](https://insights.sbomify.com/CVE-2026-106113/): ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index (high 7.5) - [CVE-2026-106115](https://insights.sbomify.com/CVE-2026-106115/): ImageSharp: TIFF CCITT T6 encoder writes beyond an undersized output buffer (high 7.5) - [CVE-2026-106117](https://insights.sbomify.com/CVE-2026-106117/): ImageSharp: CCITT fax decompression (T4/Modified Huffman): unbounded WriteBits overflows strip buffer — heap OOB write in SixLabors.ImageSharp (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32035 and fix it if it is affected. What it is: CVE-2024-32035 is a medium-severity denial of service vulnerability in SixLabors ImageSharp, published on 15 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-32035 in the wild and no public exploit code. Affected packages and fixed versions: - SixLabors.ImageSharp (NuGet): affected all versions; fixed in 2.1.8 - SixLabors.ImageSharp (NuGet): affected all versions; fixed in 2.1.8 - SixLabors.ImageSharp (NuGet): affected from 3.0.0; fixed in 3.1.4 - SixLabors.ImageSharp (NuGet): affected from 3.0.0; fixed in 3.1.4 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-32035/ (Markdown: https://insights.sbomify.com/CVE-2024-32035/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32035 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32035 - OSV: https://osv.dev/vulnerability/CVE-2024-32035 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32035/ Summaries are generated and may contain mistakes; the official description above is the record.