From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtasn1: security bump to version 4.13
Date: Thu, 8 Feb 2018 22:11:59 +0100 [thread overview]
Message-ID: <20180208221159.25192fc9@windsurf.lan> (raw)
In-Reply-To: <a055dd8302369efd8f63a769d9a6f2965b2a98da.1518115605.git.baruch@tkos.co.il>
Hello,
On Thu, 8 Feb 2018 20:46:45 +0200, Baruch Siach wrote:
> CVE-2017-10790: NULL pointer dereference and crash when reading crafted
> input
>
> CVE-2018-6003: Stack exhaustion due to indefinite recursion during BER
> decoding
>
> Add license files hashes.
>
> Cc: Stefan Fr?berg <stefan.froberg@petroprogram.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/libtasn1/libtasn1.hash | 6 +++++-
> package/libtasn1/libtasn1.mk | 2 +-
> 2 files changed, 6 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-08 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 18:46 [Buildroot] [PATCH] libtasn1: security bump to version 4.13 Baruch Siach
2018-02-08 21:11 ` Thomas Petazzoni [this message]
2018-04-10 20:43 ` 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=20180208221159.25192fc9@windsurf.lan \
--to=thomas.petazzoni@bootlin.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.