archive mirror
 help / color / mirror / Atom feed
From: Alain Michaud <>
Cc: Alain Michaud <>
Subject: [BlueZ PATCH 0/2] HID and HOGP connections from non-bonded devices.
Date: Tue, 10 Mar 2020 02:35:14 +0000	[thread overview]
Message-ID: <> (raw)

It was discovered that BlueZ's HID and HOGP profiles implementations
don't specifically require bonding between the device and the host.

This creates an opportunity for an malicious device to connect to a
target host to either impersonate an existing HID device without
security or to cause an SDP or GATT service discovery to take place
which would allow HID reports to be injected to the input subsystem from
a non-bonded source.

This patch series addresses the issue by ensuring that only connections
from devices that are bonded are accepted by the HID and HOGP profile

More information about the vulnerability is available here:

Alain Michaud (2):
  HOGP must only accept data from bonded devices.
  HID accepts bonded device connections only.

 profiles/input/device.c   | 23 ++++++++++++++++++++++-
 profiles/input/device.h   |  1 +
 profiles/input/hog.c      |  4 ++++
 profiles/input/input.conf |  8 ++++++++
 profiles/input/manager.c  | 13 ++++++++++++-
 5 files changed, 47 insertions(+), 2 deletions(-)


             reply	other threads:[~2020-03-10  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  2:35 Alain Michaud [this message]
2020-03-10  2:35 ` [BlueZ PATCH 1/2] HOGP must only accept data from bonded devices Alain Michaud
2020-03-10  6:04   ` Luiz Augusto von Dentz
2020-03-10  2:35 ` [BlueZ PATCH 2/2] HID accepts bonded device connections only Alain Michaud
2020-03-10  6:22   ` Luiz Augusto von Dentz
2020-03-10  5:24 ` [BlueZ PATCH 0/2] HID and HOGP connections from non-bonded devices Marcel Holtmann
2020-03-10  6:27   ` Luiz Augusto von Dentz
2020-03-10 12:30     ` Alain Michaud
2020-03-10 17:12       ` Luiz Augusto von Dentz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).