Bug 2122357 (CVE-2020-35532) - CVE-2020-35532 LibRaw: Out-of-bounds read in simple_decode_row() function
Summary: CVE-2020-35532 LibRaw: Out-of-bounds read in simple_decode_row() function
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2020-35532
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2122363
TreeView+ depends on / blocked
 
Reported: 2022-08-29 20:53 UTC by Pedro Sampaio
Modified: 2023-08-08 03:02 UTC (History)
18 users (show)

Fixed In Version: LibRaw 0.21-Beta1, LibRaw 0.20.2, LibRaw 0.20.1, LibRaw 0.20.0, LibRaw 0.20-RC2
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in LibRaw. An out-of-bounds read vulnerability exists within the "simple_decode_row()" function (libraw\src\x3f\x3f_utils_patched.cpp), which can be triggered via an image with a large row_stride field.
Clone Of:
Environment:
Last Closed: 2022-11-30 00:27:59 UTC
Embargoed:

Attachments (Terms of Use)

Description Pedro Sampaio 2022-08-29 20:53:13 UTC 
In LibRaw, an out-of-bounds read vulnerability exists within the "simple_decode_row()" function (libraw\src\x3f\x3f_utils_patched.cpp) which can be triggered via an image with a large row_stride field.

Upstream issue:

https://github.com/LibRaw/LibRaw/issues/271

Upstream fix:

https://github.com/LibRaw/LibRaw/commit/5ab45b085898e379fedc6b113e2e82a890602b1e
Comment 1 Debarshi Ray 2022-09-07 10:50:11 UTC 
What's the severity of this CVE?  Moderate?

For what it's worth, this CVE neither affects the LibRaw package in Fedora (F >= 35 has 0.20.2) nor in RHEL 9 (has 0.20.2).

I didn't check packages that carry other copies of the same code (eg., dcraw).
Comment 2 Product Security DevOps Team 2022-11-30 00:27:57 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-35532
Note You need to log in before you can comment on or make changes to this bug.