Bug 1956868 (CVE-2020-36332) - CVE-2020-36332 libwebp: excessive memory allocation when reading a file
Summary: CVE-2020-36332 libwebp: excessive memory allocation when reading a file
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-36332
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1962004 1962005 1961603 1961604 1961978 1961979
Blocks: 1940150 1956995
TreeView+ depends on / blocked
 
Reported: 2021-05-04 14:52 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-04-17 21:21 UTC (History)
9 users (show)

Fixed In Version: libwebp 1.0.1
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in libwebp. When reading a file libwebp allocates an excessive amount of memory. The highest threat from this vulnerability is to the service availability.
Clone Of:
Environment:
Last Closed: 2021-11-10 01:52:23 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4231 0 None None None 2021-11-09 17:50:26 UTC

Description Guilherme de Almeida Suckevicz 2021-05-04 14:52:29 UTC 
A flaw was found in libwebp in versions before 1.0.1 in the way it read the contents of a file without limiting memory allocation.

Reference:
https://bugs.chromium.org/p/webp/issues/detail?id=391
Comment 1 Riccardo Schirone 2021-05-18 10:25:18 UTC 
Upstream patch:
https://chromium.googlesource.com/webm/libwebp/+/39cb9aad85ca7bb1d193013460db1f8cc6bff109
Comment 5 errata-xmlrpc 2021-11-09 17:50:25 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:4231 https://access.redhat.com/errata/RHSA-2021:4231
Comment 6 Product Security DevOps Team 2021-11-10 01:52:21 UTC 
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-36332
Note You need to log in before you can comment on or make changes to this bug.