GitHub Advisoryadvisory · NuGet

GHSA-qxrv-gp6x-rc23 SixLabors ImageSharp has Excessive Memory Allocation in Gif Decoder

MEDIUM Published 2024-07-22 Modified 2024-09-11 Official page ↗
Aliases
CVE-2024-41132
Ecosystem
NuGet
Packages
SixLabors.ImageSharp
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weaknesses
CWE-770, CWE-789
Reviewed
2024-07-22

Affected packages

• NuGet SixLabors.ImageSharp: < 2.1.9 → fixed in 2.1.9 • NuGet SixLabors.ImageSharp: >= 3.0.0, < 3.1.5 → fixed in 3.1.5

Description

Impact _What kind of vulnerability is it? Who is impacted?_ A vulnerability discovered in the ImageSharp library, where the processing of specially crafted files can lead to excessive memory usage in the Gif decoder. The vulnerability is triggered when ImageSharp attempts to process image files that are designed to exploit this flaw. Patches _Has the problem been patched? What versions should users upgrade to?_ The problem has been patched. All users are advised to upgrade to v3.1.5 or v2.1.9. Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Before calling `Image.Decode(Async)`, use `Image.Identify` to determine the image dimensions in order to enforce a limit. References _Are there any links users can visit to find out more?_ • https://github.com/SixLabors/ImageSharp/pull/2759 • https://github.com/SixLabors/ImageSharp/pull/2764 • https://github.com/SixLabors/ImageSharp/pull/2770 • ImageSharp: Security Considerations • ImageSharp.Web: Securing Processing Commands

Related

Alias · CVE (1)

Weakness · CWE (2)

  • CWE-770 Allocation of Resources Without Limits or Throttling weakness
  • CWE-789 Memory Allocation with Excessive Size Value weakness

References