Skip to content

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

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

References

@JimBobSquarePants JimBobSquarePants published to SixLabors/ImageSharp Apr 15, 2024
Published by the National Vulnerability Database Apr 15, 2024
Published to the GitHub Advisory Database Apr 15, 2024
Reviewed Apr 15, 2024
Last updated Apr 15, 2024

Severity

Moderate
5.3
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Weaknesses

CVE ID

CVE-2024-32035

GHSA ID

GHSA-g85r-6x2q-45w7

Source code

Credits

Checking history
See something to contribute? Suggest improvements for this vulnerability.