From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/bluez5_utils: security bump version to 5.47
Date: Sun, 17 Sep 2017 18:52:45 +0200 [thread overview]
Message-ID: <20170917185245.6c2eac0b@windsurf> (raw)
In-Reply-To: <20170916084117.11155-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 16 Sep 2017 10:41:17 +0200, Bernd Kuhls wrote:
> Fixes CVE-2017-1000250 - All versions of the SDP server in BlueZ 5.46 and
> earlier are vulnerable to an information disclosure vulnerability which
> allows remote attackers to obtain sensitive information from the bluetoothd
> process memory. This vulnerability lies in the processing of SDP search
> attribute requests.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/bluez5_utils/bluez5_utils.hash | 2 +-
> package/bluez5_utils/bluez5_utils.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-17 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 8:41 [Buildroot] [PATCH 1/1] package/bluez5_utils: security bump version to 5.47 Bernd Kuhls
2017-09-17 16:52 ` Thomas Petazzoni [this message]
2017-10-16 21:55 ` 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=20170917185245.6c2eac0b@windsurf \
--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