From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: security bump to 3.6.7.1
Date: Sun, 07 Apr 2019 22:54:25 +0200 [thread overview]
Message-ID: <87a7h1ilj2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190403061405.27273-1-stefan.sorensen@spectralink.com> (=?utf-8?Q?=22S=C3=B8rensen=2C?= Stefan"'s message of "Wed, 3 Apr 2019 06:14:32 +0000")
>>>>> "S?rensen," == S?rensen, Stefan <Stefan.Sorensen@spectralink.com> writes:
> Fixes the following security issues:
> * CVE-2019-3836: It was discovered in gnutls before version 3.6.7 upstream
> that there is an uninitialized pointer access in gnutls versions 3.6.3 or
> later which can be triggered by certain post-handshake messages
> * CVE-2019-3829: A vulnerability was found in gnutls versions from 3.5.8
> before 3.6.7. A memory corruption (double free) vulnerability in the
> certificate verification API. Any client or server application that
> verifies X.509 certificates with GnuTLS 3.5.8 or later is affected.
> Signed-off-by: Stefan S?rensen <stefan.sorensen@spectralink.com>
Committed after fixing the license file hash and adding a note that
3.6.7.1 fixes a tarball packaging issue, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-04-07 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 6:14 [Buildroot] [PATCH] gnutls: security bump to 3.6.7.1 Sørensen, Stefan
2019-04-03 8:01 ` Peter Korsgaard
2019-04-03 8:11 ` Sørensen, Stefan
2019-04-03 19:56 ` Thomas Petazzoni
2019-04-07 20:54 ` Peter Korsgaard [this message]
2019-04-14 21:17 ` 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=87a7h1ilj2.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.