Bug 1984051 (CVE-2020-36427)

Summary: CVE-2020-36427 gthumb: DoS via malformed JPEG image
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: caillon+fedoraproject, carl, chkr, gnome-sig, mclasen, rhughes, rstrode, sandmann
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gthumb 3.10.1 Doc Type: If docs needed, set a value
Doc Text:
There's a flaw in gThumb. An attacker who is able to trick a victim into opening a specially crafted file with gThumb could trigger a crash via assertion failure or memory leak. The greatest impact of this flaw is to application availability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-29 19:06:56 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: 1984052    
Bug Blocks: 1984053    

Description Guilherme de Almeida Suckevicz 2021-07-20 14:04:56 UTC
GNOME gThumb before 3.10.1 allows an application crash via a malformed JPEG image.

Reference:
https://mail.gnome.org/archives/gthumb-list/2020-September/msg00001.html

Comment 1 Guilherme de Almeida Suckevicz 2021-07-20 14:05:24 UTC
Created gthumb tracking bugs for this issue:

Affects: epel-7 [bug 1984052]

Comment 2 Todd Cullum 2021-07-29 17:55:53 UTC
Pretty sure this is the upstream patch commit: https://gitlab.gnome.org/GNOME/gthumb/-/commit/9729b8688d5d67c01deabea46ad469ec517250c5 . Please see commit message there for more details.

Comment 3 Todd Cullum 2021-07-29 18:02:18 UTC
Upstream issue with more details and reproduction info: https://gitlab.gnome.org/GNOME/gthumb/-/issues/106

Comment 4 Product Security DevOps Team 2021-07-29 19:06:56 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-36427