Headline
GHSA-g85r-6x2q-45w7: SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value
Impact
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.
Patches
The problem has been patched. All users are advised to upgrade to v3.1.4 or v2.1.8.
Workarounds
Before calling Image.Decode(Async), use Image.Identify to determine the image dimensions in order to enforce a limit.
References
- ImageSharp: Security Considerations
- ImageSharp.Web: Securing Processing Commands
Skip to content
Actions
Automate any workflow
Packages
Host and manage packages
Security
Find and fix vulnerabilities
Codespaces
Instant dev environments
Copilot
Write better code with AI
Code review
Manage code changes
Issues
Plan and track work
Discussions
Collaborate outside of code
GitHub Sponsors
Fund open source developers
* The ReadME Project
GitHub community articles
- Pricing
Provide feedback
Saved searches****Use saved searches to filter your results more quickly
Sign up
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2024-32035
SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value
Moderate severity GitHub Reviewed Published Apr 15, 2024 in SixLabors/ImageSharp • Updated Apr 15, 2024
Package
nuget SixLabors.ImageSharp (NuGet)
Affected versions
< 2.1.8
>= 3.0.0, < 3.1.4
Patched versions
2.1.8
3.1.4
Description
Published to the GitHub Advisory Database
Apr 15, 2024
Last updated
Apr 15, 2024