Skip to content

Commit

Permalink
Updated capitalisation [ci skip]
Browse files Browse the repository at this point in the history
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
  • Loading branch information
radarhere and hugovk committed Jan 2, 2021
1 parent 95f99d5 commit d88fdcd
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/releasenotes/8.1.0.rst
Expand Up @@ -38,25 +38,25 @@ Security

This release includes security fixes.

* An out-of-bounds read when saving TIFFs with custom metadata through libtiff
* An out-of-bounds read when saving TIFFs with custom metadata through LibTIFF
* An out-of-bounds read when saving a GIF of 1px width
* :cve:`CVE-2020-35653` Buffer Read Overrun in PCX Decoding.
* :cve:`CVE-2020-35653` Buffer read overrun in PCX decoding

The PCX Image decoder used the reported image stride to calculate the row buffer,
The PCX image decoder used the reported image stride to calculate the row buffer,
rather than calculating it from the image size. This issue dates back to the PIL fork.
Thanks to Google's OSS-Fuzz project for finding this.

* :cve:`CVE-2020-35654` Fix TIFF OOB Write error

OOB Write in TiffDecode.c when reading corrupt YCbCr files in some LibTiff versions
(4.1.0/Ubuntu 20.04, but not 4.0.9/Ubuntu 18.04). In some cases libtiff's
OOB Write in TiffDecode.c when reading corrupt YCbCr files in some LibTIFF versions
(4.1.0/Ubuntu 20.04, but not 4.0.9/Ubuntu 18.04). In some cases LibTIFF's
interpretation of the file is different when reading in RGBA mode, leading to an Out of
bounds write in TiffDecode.c. This potentially affects Pillow versions from 6.0.0 to
8.0.1, depending on the version of LibTiff. This was reported through Tidelift.
8.0.1, depending on the version of LibTIFF. This was reported through Tidelift.

* :cve:`CVE-2020-35655` Fix for SGI Decode buffer overrun

4 Byte Read Overflow in SGIRleDecode.c, where the code was not correctly checking the
4 byte read overflow in SGIRleDecode.c, where the code was not correctly checking the
offsets and length tables. Independently reported through Tidelift and Google's OSS-Fuzz.
This vulnerability covers Pillow versions 4.3.0->8.0.1.

Expand Down

0 comments on commit d88fdcd

Please sign in to comment.