SixLabors.ImageSharp vulnerabilities
A new, fully featured, fully managed, cross-platform, 2D graphics API for .NET
- Registry
- NuGet
- Latest
- 4.1.3
15 known advisories
The latest version, 4.1.3, is not affected by any of them. Projects on older versions may be.
dotnet add package SixLabors.ImageSharp --version 4.1.3Is your project on an affected SixLabors.ImageSharp?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for SixLabors.ImageSharp
ImageSharp: TIFF CCITT T6 encoder writes beyond an undersized output buffer
- Affected
- >=2.1.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: EXR ZIP decoder can expose stale allocator data after a short inflate
- Affected
- >=4.0.0 <4.1.2
- Fixed in
- 4.1.2
ImageSharp: ICC LUT16 output channel count can write beyond Vector4
- Affected
- >=4.0.0 <4.1.2
- Fixed in
- 4.1.2
ImageSharp: BigTIFF IFD count can keep a decoder thread in a non-progressing loop
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: HistogramEqualization uses an unvalidated luminance as an unchecked histogram index
- Affected
- >=2.0.0 <3.2.0 · >=4.0.0 <4.1.2
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: ICC CLUT parsing allocates from unvalidated channel and grid dimensions
- Affected
- >=4.0.0 <4.1.2 · >=1.0.0-beta0001 <3.2.0
- Fixed in
- 3.2.0, 4.1.2
ImageSharp: Tiled fax TIFF: tile buffer sized by TileWidth but fax decompressor writes scanlines of ImageWidth — heap OOB write
- Affected
- >=3.0.0 <3.2.0 · >=4.0.0 <4.1.1
- Fixed in
- 3.2.0, 4.1.1
SixLabors ImageSharp Has Infinite Loop in GIF Decoder When Skipping Malformed Comment Extension Blocks
- Affected
- <2.1.11 · >=3.0.0 <3.1.11
- Fixed in
- 2.1.11, 3.1.11
Out-of-bounds Write in SixLabors ImageSharp
- Affected
- >=3.0.0 <3.1.7 · <2.1.10
- Fixed in
- 2.1.10, 3.1.7
SixLabors ImageSharp has Excessive Memory Allocation in Gif Decoder
- Affected
- <2.1.9 · >=3.0.0 <3.1.5
- Fixed in
- 2.1.9, 3.1.5
SixLabors ImageSharp Out-of-bounds Write
- Affected
- <2.1.9 · >=3.0.0 <3.1.5
- Fixed in
- 2.1.9, 3.1.5
SixLabors.ImageSharp vulnerable to data leakage
- Affected
- <2.1.8 · >=3.0.0 <3.1.4
- Fixed in
- 2.1.8, 3.1.4
SixLabors.ImageSharp vulnerable to Memory Allocation with Excessive Size Value
- Affected
- <2.1.8 · >=3.0.0 <3.1.4
- Fixed in
- 2.1.8, 3.1.4
Use After Free in SixLabors.ImageSharp
- Affected
- >=3.0.0 <3.1.3 · <2.1.7
- Fixed in
- 2.1.7, 3.1.3
Is your SixLabors.ImageSharp version vulnerable?
- SixLabors.ImageSharp 4.1No known advisories in 4.1.3
- SixLabors.ImageSharp 4.08 advisories in 4.0.0
- SixLabors.ImageSharp 3.2No known advisories in 3.2.0
- SixLabors.ImageSharp 3.16 advisories in 3.1.12
- SixLabors.ImageSharp 3.013 advisories in 3.0.2
- SixLabors.ImageSharp 2.15 advisories in 2.1.13
- SixLabors.ImageSharp 2.011 advisories in 2.0.0
Which of your client projects still run an old SixLabors.ImageSharp?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.