Your submission was sent successfully! Close

CVE-2021-27921

Published: 3 March 2021

Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for a BLP container, and thus an attempted memory allocation can be very large.

Notes

AuthorNote
mdeslaur
while this is mentioned in the 8.1.1 release notes, it doesn't
seem to be mentioned in the CHANGES file, and I can't seem to
locate the commits that fix this in 8.1.1 vs 8.1.0
This was actually fixed in 8.1.2.
Priority

Medium

CVSS 3 base score: 7.5

Status

Package Release Status
pillow
Launchpad, Ubuntu, Debian
bionic
Released (5.1.0-1ubuntu0.5)
focal
Released (7.0.0-4ubuntu0.3)
groovy
Released (7.2.0-1ubuntu0.2)
hirsute Not vulnerable
(8.1.2-1)
impish Not vulnerable
(8.1.2-1)
jammy Not vulnerable
(8.1.2-1)
precise Does not exist

trusty Not vulnerable
(code not present)
upstream
Released (8.1.2)
xenial Not vulnerable
(code not present)
Patches:
upstream: https://github.com/python-pillow/Pillow/commit/480f6819b592d7f07b9a9a52a7656c10bbe07442
pillow-python2
Launchpad, Ubuntu, Debian
bionic Does not exist

focal Needs triage

groovy Ignored
(reached end-of-life)
hirsute Does not exist

impish Does not exist

jammy Does not exist

precise Does not exist

trusty Does not exist

upstream Needs triage

xenial Does not exist

python-imaging
Launchpad, Ubuntu, Debian
bionic Does not exist

focal Does not exist

groovy Does not exist

hirsute Does not exist

impish Does not exist

jammy Does not exist

precise Ignored
(end of ESM support, was needs-triage)
trusty Does not exist

upstream Needs triage

xenial Does not exist