Patchfirst
ChainSixLabors · ImageSharpNuGet:SixLabors.ImageSharp

SixLabors ImageSharp: successive fixes (2024)

3 CVEs over 2 generations, 15 Apr 2024 to 22 Jul 2024.

Family tree

Left to right by publication date.Oldest first. Select a CVE to open it.
  1. CVE-2024-3203515 Apr 2024 First in the chain
  2. CVE-2024-4113122 Jul 2024 next fix after CVE-2024-32035
  3. CVE-2024-4113222 Jul 2024 next fix after CVE-2024-32035related to CVE-2024-41131
Apr 2024Jul CVE-2024-32035 → CVE-2024-41132: Next fix in the same package (medium confidence)CVE-2024-41131 → CVE-2024-41132: related (medium confidence)CVE-2024-32035 → CVE-2024-41131: Next fix in the same package (low confidence) CVE-2024-32035 15 Apr 2024 CVE-2024-41131 22 Jul 2024 CVE-2024-41132 22 Jul 2024 Apr 2024JunJul CVE-2024-32035 → CVE-2024-41132: Next fix in the same package (medium confidence)CVE-2024-41131 → CVE-2024-41132: related (medium confidence)CVE-2024-32035 → CVE-2024-41131: Next fix in the same package (low confidence) CVE-2024-32035 15 Apr 2024 CVE-2024-41131 22 Jul 2024 CVE-2024-41132 22 Jul 2024
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low

CVEs in this family

Table view of the tree
CVEPublishedTitleLinked fromPriority
CVE-2024-32035 15 Apr 2024 Memory Allocation with Excessive Size Value in SixLabors.ImageSharp · fixed in 3.1.4 First in chain 13.7
CVE-2024-41131 22 Jul 2024 Out-of-bounds Write in SixLabors ImageSharp · fixed in 3.1.5 CVE-2024-32035 · Next fix in the same package · Low 15.6
CVE-2024-41132 22 Jul 2024 SixLabors ImageSharp Allows Excessive Memory Allocation in Gif Decoder · fixed in 3.1.5 CVE-2024-32035 · Next fix in the same package · Medium 14.9
↑ ↓ chooseEnter openEsc close