Bug 1089109 - (CVE-2018-3837) VUL-0: CVE-2018-3837: SDL_image,SDL2_image: An exploitable information disclosure vulnerability exists in the PCX imagerendering functionality of Simple DirectMedia Layer SDL2_image-2.0.2. Aspecially crafted PCX image can cause an out-of-bounds read
(CVE-2018-3837)
VUL-0: CVE-2018-3837: SDL_image,SDL2_image: An exploitable information disclo...
Status: RESOLVED FIXED
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: Alexander Herzig
Security Team bot
https://smash.suse.de/issue/203581/
CVSSv3:SUSE:CVE-2018-3837:3.3:(AV:L/A...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-11 13:37 UTC by Marcus Meissner
Modified: 2020-11-10 21:22 UTC (History)
3 users (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 Marcus Meissner 2018-04-11 13:37:59 UTC
CVE-2018-3837

An exploitable information disclosure vulnerability exists in the PCX image
rendering functionality of Simple DirectMedia Layer SDL2_image-2.0.2. A
specially crafted PCX image can cause an out-of-bounds read on the heap,
resulting in information disclosure . An attacker can display a specially
crafted image to trigger this vulnerability.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-3837
https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0519
Comment 1 Jan Engelhardt 2018-06-04 09:09:31 UTC
Probably fixed, but no way of knowing since the report is lacking a reproducer, and the SCM commits don't mention any CVE/etc. IDs.
Comment 2 Marcus Meissner 2018-06-25 12:35:45 UTC
https://hg.libsdl.org/SDL_image/rev/2938fc80591a

seems the fix for it, is in 2.0.3.
Comment 3 Marcus Meissner 2018-06-25 12:40:06 UTC
42.3, 15.0 and factory is fixed with 2.0.3.

in sle11 it is only in the SDK and not likely used at all, so we can close.