Bug 1215715 (CVE-2023-5129) - VUL-0: CVE-2023-5129: libwebp: With a specially crafted WebP lossless file, libwebp may write data out of bounds to the heap
Summary: VUL-0: CVE-2023-5129: libwebp: With a specially crafted WebP lossless file, l...
Status: RESOLVED DUPLICATE of bug 1215231
Alias: CVE-2023-5129
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Critical
Target Milestone: ---
Assignee: E-mail List
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/379829/
Whiteboard: CVSSv3.1:SUSE:CVE-2023-5129:8.8:(AV:N...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-26 09:22 UTC by SMASH SMASH
Modified: 2023-09-26 09:35 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2023-09-26 09:22:41 UTC
With a specially crafted WebP lossless file, libwebp may write data out of
bounds to the heap.

The ReadHuffmanCodes() function allocates the HuffmanCode buffer with a size
that comes from an array of precomputed sizes: kTableSize. The color_cache_bits
value defines which size to use.

The kTableSize array only takes into account sizes for 8-bit first-level table
lookups but not second-level table lookups. libwebp allows codes that are up to
15-bit (MAX_ALLOWED_CODE_LENGTH). When BuildHuffmanTable() attempts to fill the
second-level tables it may write data out-of-bounds. The OOB write to the
undersized array happens in ReplicateValue.



References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5129
https://chromium.googlesource.com/webm/libwebp/+/2af26267cdfcb63a88e5c74a85927a12d6ca1d76
https://chromium.googlesource.com/webm/libwebp/+/902bc9190331343b2017211debcec8d2ab87e17a
Comment 1 Cathy Hu 2023-09-26 09:35:10 UTC
this is already tracked internally via bsc#1215231, marking as duplicate

*** This bug has been marked as a duplicate of bug 1215231 ***