Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 639988 (CVE-2017-1000410) - kernel: BT info leak
Summary: kernel: BT info leak
Status: IN_PROGRESS
Alias: CVE-2017-1000410
Product: Gentoo Security
Classification: Unclassified
Component: Kernel (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Kernel Security
URL: http://www.openwall.com/lists/oss-sec...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-05 22:53 UTC by Thomas Deutschmann
Modified: 2017-12-10 01:22 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deutschmann gentoo-dev Security 2017-12-05 22:53:01 UTC
Incoming details.
Comment 1 Alice Ferrazzi Gentoo Infrastructure gentoo-dev 2017-12-06 06:40:32 UTC
thanks you
Comment 2 Thomas Deutschmann gentoo-dev Security 2017-12-06 16:32:57 UTC
From $URL:

Hello,

We are writing to disclose an information leak vulnerability in the
Bluetooth stack of the Linux Kernel (BlueZ).
This vulnerability has been disclosed to the Kernel's security team (
security@...nel.org), and a patch for it is in stages of review.
This patch is also attached here.

This vulnerability lies in the processing of incoming L2CAP commands -
ConfigRequest, and ConfigResponse messages.
This info leak is a result of uninitialized stack variables that may be
returned to an attacker in their uninitialized state.
By manipulating the code flows that precede the handling of these
configuration messages, an attacker can also gain some control over which
data will be held in the uninitialized stack variables.
This can allow him to bypass KASLR, and stack canaries protection - as both
pointers and stack canaries may be leaked in this manner.

Combining this vulnerability (for example) with the previously disclosed
RCE vulnerability in L2CAP configuration parsing (CVE-2017-1000251) may
allow an attacker to exploit the RCE against kernels which were built with
the above mitigations.

These are the specifics of this vulnerability:
In the function l2cap_parse_conf_rsp and in the function
l2cap_parse_conf_req the following variable is declared without
initialization:

struct l2cap_conf_efs efs;

In addition, when parsing input configuration parameters in both of these
functions, the switch case for handling EFS elements may skip the memcpy
call that will write to the efs variable:

...
case L2CAP_CONF_EFS:
if (olen == sizeof(efs))
memcpy(&efs, (void *)val, olen);
...

The olen in the above if is attacker controlled, and regardless of that if,
in both of these functions the efs variable would eventually be added to
the outgoing configuration request that is being built:

l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS, sizeof(efs), (unsigned long) &efs);

So by sending a configuration request, or response, that contains an
L2CAP_CONF_EFS element, but with an element length that is not sizeof(efs)
- the memcpy to the uninitialized efs variable can be avoided,
and the uninitialized variable would be returned to the attacker (16 bytes).

A simple patch for avoiding this info leak is attached.

Ben Seri,
Armis