Bug 1789532 (CVE-2020-5313)
Summary: | CVE-2020-5313 python-pillow: out-of-bounds read in ImagingFliDecode when loading FLI images | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Pedro Sampaio <psampaio> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | bdettelb, cstratak, dbecker, jjoyce, jschluet, jschorr, lbalhar, lhh, lpeer, manisandro, mburns, miminar, orion, python-maint, sclewis, slinaber, tomckay, torsava, tsmetana |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | python-pillow 6.2.2 | Doc Type: | If docs needed, set a value |
Doc Text: |
An out-of-bounds read was discovered in python-pillow in the way it decodes FLI images. An application that uses python-pillow to load untrusted images may be vulnerable to this flaw, which can allow an attacker to read the memory of the application they should be not allowed to read.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-28 19:28:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1789541, 1789542, 1799351, 1799352, 1857524 | ||
Bug Blocks: | 1789544 |
Description
Pedro Sampaio
2020-01-09 18:47:24 UTC
Created python-pillow tracking bugs for this issue: Affects: fedora-all [bug 1789541] Created python3-pillow tracking bugs for this issue: Affects: epel-7 [bug 1789542] While Red Hat Quay includes the python-pillow it's not used, therefore this issue is rated moderate for Red Hat Quay. Function ImagingFliDecode() in FliDecode.c uses a buffer `buf` of `bytes` bytes as input. However, it tries to read 2 bytes from the buffer+4 when it was only checked that the buffer contained at least 4 bytes. If the size of the buffer is 4, for example, the additional 2 bytes would be read from the memory after the allocated buffer. This can result in an out-of-bound read, which could be used to leak some memory data from the program or, at most, make it crash. This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:3185 https://access.redhat.com/errata/RHSA-2020:3185 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-5313 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:3887 https://access.redhat.com/errata/RHSA-2020:3887 This issue has been addressed in the following products: Red Hat Quay 3 Via RHSA-2021:0420 https://access.redhat.com/errata/RHSA-2021:0420 |