golang.org/x/image

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.

VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

The TIFF decoder can panic when decoding an invalid image with an out-of-bounds strip offset.

The TIFF decoder does not set a limit on the size of tiles in tiled images, permitting a malicious or corrupt image containing a very large tile to cause unbounded memory consumption.

The webp decoder can panic when processing a VP8 chunk with dimensions that do not match the canvas size.

Decoding a paletted BMP file with an out-of-range palette index results in a panic when accessing pixels in the invalid image.

Parsing a malicious font file can cause excessive memory allocation.

Parsing a WEBP image with an invalid, large size panics on 32-bit platforms.

A maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.