Bug 1739409 (CVE-2019-5060) - CVE-2019-5060 SDL2_image: exploitable code execution in the XPM image rendering leads to an integer overflow in the colorhash function
Summary: CVE-2019-5060 SDL2_image: exploitable code execution in the XPM image renderi...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-5060
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1739410 1739411 1739412 1739413
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-09 09:07 UTC by Marian Rehak
Modified: 2021-02-16 21:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-09 13:18:25 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Rehak 2019-08-09 09:07:21 UTC 
An exploitable code execution vulnerability exists in the XPM image rendering function of SDL2_image 2.0.4. A specially crafted XPM image can cause an integer overflow in the colorhash function, allocating too small of a buffer. This buffer can then be written out of bounds, resulting in a heap overflow, ultimately ending in code execution. An attacker can display a specially crafted image to trigger this vulnerability.

External References:

https://talosintelligence.com/vulnerability_reports/TALOS-2019-0844
Comment 1 Marian Rehak 2019-08-09 09:09:23 UTC 
Created SDL2_image tracking bugs for this issue:

Affects: epel-7 [bug 1739410]
Affects: fedora-all [bug 1739412]


Created mingw-SDL2_image tracking bugs for this issue:

Affects: epel-all [bug 1739411]
Affects: fedora-all [bug 1739413]
Comment 2 Product Security DevOps Team 2019-08-09 13:18:25 UTC 
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note You need to log in before you can comment on or make changes to this bug.