From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] sdl2_image: security bump to version 2.0.3
Date: Tue, 01 May 2018 09:33:58 +0200 [thread overview]
Message-ID: <87sh7bj0d5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180430120459.8438-2-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 30 Apr 2018 14:04:59 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> CVE-2017-12122: An exploitable code execution vulnerability exists in the
> ILBM image rendering functionality of SDL2_image-2.0.2. A specially crafted
> ILBM image can cause a heap overflow resulting in code execution. An
> attacker can display a specially crafted image to trigger this
> vulnerability.
> CVE-2017-14440: An exploitable code execution vulnerability exists in the
> ILBM image rendering functionality of SDL2_image-2.0.2. A specially crafted
> ILBM image can cause a stack overflow resulting in code execution. An
> attacker can display a specially crafted image to trigger this
> vulnerability.
> CVE-2017-14441: An exploitable code execution vulnerability exists in the
> ICO image rendering functionality of SDL2_image-2.0.2. A specially crafted
> ICO image can cause an integer overflow, cascading to a heap overflow
> resulting in code execution. An attacker can display a specially crafted
> image to trigger this vulnerability.
> CVE-2017-14442: An exploitable code execution vulnerability exists in the
> BMP image rendering functionality of SDL2_image-2.0.2. A specially crafted
> BMP image can cause a stack overflow resulting in code execution. An
> attacker can display a specially crafted image to trigger this
> vulnerability.
> CVE-2017-14448: An exploitable code execution vulnerability exists in the
> XCF image rendering functionality of SDL2_image-2.0.2. A specially crafted
> XCF image can cause a heap overflow resulting in code execution. An
> attacker can display a specially crafted image to trigger this
> vulnerability.
> CVE-2017-14449: A double-Free vulnerability exists in the XCF image
> rendering functionality of SDL2_image-2.0.2. A specially crafted XCF image
> can cause a Double-Free situation to occur. An attacker can display a
> specially crafted image to trigger this vulnerability.
> CVE-2017-14450: A buffer overflow vulnerability exists in the GIF image
> parsing functionality of SDL2_image-2.0.2. A specially crafted GIF image
> can lead to a buffer overflow on a global section. An attacker can display
> an image to trigger this vulnerability.
> For details, see the announcement:
> https://discourse.libsdl.org/t/sdl-image-2-0-3-released/23958
> Also add a hash for the license file while we're at it.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-01 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 12:04 [Buildroot] [PATCH 1/2] sdl2: bump version to 2.0.8 Peter Korsgaard
2018-04-30 12:04 ` [Buildroot] [PATCH 2/2] sdl2_image: security bump to version 2.0.3 Peter Korsgaard
2018-05-01 7:33 ` Peter Korsgaard [this message]
2018-04-30 15:41 ` [Buildroot] [PATCH 1/2] sdl2: bump version to 2.0.8 Thomas Petazzoni
2018-05-01 7:33 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh7bj0d5.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.