SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value
GHSA-g85r-6x2q-45w7 · CVE-2024-32035
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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
References
- WEB https://github.com/SixLabors/ImageSharp/security/advisories/GHSA-g85r-6x2q-45w7
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2024-32035
- WEB https://github.com/SixLabors/ImageSharp/commit/b6b08ac3e7cea8da5ac1e90f7c0b67dd254535c3
- WEB https://github.com/SixLabors/ImageSharp/commit/f21d64188e59ae9464ff462056a5e29d8e618b27
- WEB https://docs.sixlabors.com/articles/imagesharp.web/processingcommands.html#securing-processing-commands
- WEB https://docs.sixlabors.com/articles/imagesharp/security.html
- PACKAGE https://github.com/SixLabors/ImageSharp
Ready to move
Start Securing
Free, no credit card | First findings in minutes