From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freetype: add upstream security fixes for CVE-2017-8105 and CVE-2017-8287
Date: Sun, 30 Apr 2017 23:07:47 +0200 [thread overview]
Message-ID: <20170430230747.28196b95@free-electrons.com> (raw)
In-Reply-To: <20170430193602.1577-1-peter@korsgaard.com>
Hello,
On Sun, 30 Apr 2017 21:36:02 +0200, Peter Korsgaard wrote:
> Add upstream post-2.7.1 commits (except for ChangeLog modifications) fixing
> the following security issues:
>
> CVE-2017-8105 - FreeType 2 before 2017-03-24 has an out-of-bounds write
> caused by a heap-based buffer overflow related to the
> t1_decoder_parse_charstrings function in psaux/t1decode.c.
>
> CVE-2017-8287 - FreeType 2 before 2017-03-26 has an out-of-bounds write
> caused by a heap-based buffer overflow related to the
> t1_builder_close_contour function in psaux/psobjs.c.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> .../0001-psaux-Better-protect-flex-handling.patch | 47 ++++++++++++++++++++++
> ...sobjs.c-t1_builder_close_contour-Add-safe.patch | 35 ++++++++++++++++
> 2 files changed, 82 insertions(+)
> create mode 100644 package/freetype/0001-psaux-Better-protect-flex-handling.patch
> create mode 100644 package/freetype/0002-src-psaux-psobjs.c-t1_builder_close_contour-Add-safe.patch
Applied, thanks! Obviously for the LTS branch as well.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-30 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 19:36 [Buildroot] [PATCH] freetype: add upstream security fixes for CVE-2017-8105 and CVE-2017-8287 Peter Korsgaard
2017-04-30 21:07 ` Thomas Petazzoni [this message]
2017-05-01 7:20 ` 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=20170430230747.28196b95@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox