From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] polarssl: security bump to version 1.2.18
Date: Thu, 12 Nov 2015 22:41:38 +0100 [thread overview]
Message-ID: <877flmopyl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1447356646-19912-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 12 Nov 2015 16:30:46 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> Fixes a potential heap corruption on Windows when
> mbedtls_x509_crt_parse_path() is passed a path longer than 2GB. This
> cannot be triggered remotely. Found by Guido Vranken, Intelworks.
> Fixes a potential buffer overflow in some asn1_write_xxx() functions.
> This cannot be triggered remotely unless you create X.509 certificates
> based on untrusted input or write keys of untrusted origin. Found by
> Guido Vranken, Intelworks.
> The X509 max_pathlen constraint was not enforced on intermediate
> certificates. Found by Nicholas Wilson, and fix and tests provided by
> Janos Follath.
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-11-12 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 19:30 [Buildroot] [PATCH] polarssl: security bump to version 1.2.18 Gustavo Zacarias
2015-11-12 21:41 ` Peter Korsgaard [this message]
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=877flmopyl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox