From: Matias Karhumaa <matias.karhumaa@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 00/12] btmon: multiple memory management vulnerabilities fixed
Date: Tue, 16 Oct 2018 23:19:08 +0300 [thread overview]
Message-ID: <20181016201908.GA84982@Matias-MacBook-Air.local> (raw)
Multiple different memory management vulnerabilities were discovered in
btmon while fuzzing it with American Fuzzy Lop. Purpose of this fuzzing
effort was to find some bugs in btmon, analyse and fix them but also try
to exploit them. Also goal was to prove that fuzzing is low effort way
to find bugs that could end up being severe ones.
Most common weakness appeared to be buffer over-read which was usually
caused by missing boundary checks before accessing array. Integer
underflows were also quite common. Most interesting bug was simple
buffer overflow that was actually discovered already couple years ago
by op7ic: https://www.spinics.net/lists/linux-bluetooth/msg68898.html
but it was still not fixed. This particular vulnerability ended up being
quite easily exploitable if certain mitigation technics were disabled.
Matias Karhumaa (12):
btmon: fix segfault caused by buffer over-read
btmon: fix segfault caused by buffer over-read
btmon: fix segfault caused by buffer over-read
btmon: Fix crash caused by integer underflow
btmon: fix stack buffer overflow
btmon: fix multiple segfaults
btmon: fix segfault caused by integer underflow
btmon: fix segfault caused by integer undeflow
btmon: fix segfault caused by buffer over-read
btmon: fix segfault caused by buffer overflow
btmon: fix segfault caused by integer underflow
btmon: fix segfault caused by buffer over-read
monitor/packet.c | 56 +++++++++++++++++++++++++++++++++++++++++---
monitor/sdp.c | 21 ++++++++++++++++-
src/shared/btsnoop.c | 5 ++++
3 files changed, 78 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-16 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 20:19 Matias Karhumaa [this message]
2018-10-18 16:11 ` [PATCH 00/12] btmon: multiple memory management vulnerabilities fixed Johan Hedberg
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=20181016201908.GA84982@Matias-MacBook-Air.local \
--to=matias.karhumaa@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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