Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Network Security

11/5/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

'BLEEDINGBIT' Bluetooth Vulnerability Leaves Enterprises Exposed to Attacks

Security firm Armis has found two, zero-day vulnerabilities in the BLE protocol of Texas Instrument chips that researchers call 'BLEEDINGBIT.'

Armis, a security firm which has already found vulnerabilities with Bluetooth, has found two additional zero-day vulnerabilities that can affect 70% to 80% of businesses through Cisco, Meraki and Aruba wireless access points (APs), which are widely used by enterprises.

The BLE protocol -- also known as Bluetooth Smart -- is based on the standard Bluetooth communications protocol but has been modified for Internet of Things (IoT) devices. It is used for access point networking, smart home locks, phone as-a-key connected systems, tracking systems as well as medical devices.

Armis detailed these two vulnerabilities, which the firm calls "BLEEDINGBIT," in a a blog post.

One problem (CVE-2018-16986) affects Cisco and Meraki APs that make use of Texas Instruments BLE chips. The Specific chips that are vulnerable include the CC2640 (non-R2) with BLE-STACK version 2.2.1 or earlier, CC2650 with BLE-STACK version 2.2.1 or earlier and CC2640R2 with BLE-STACK version 1.0 or earlier.

TI chips that are not affected include Automotive Qualified CC2640R2F-Q1, CC2540/CC2541 devices on any BLE-STACK version, CC2640R2 SDK version 1.30.00.25 or greater, CC1352/CC26x2 on any supported SDK version and CC2640 or CC2650 on any supported BLE-STACK SDK version 2.2.2. In general, any device configuration that doesn't perform BLE scanning -- that is, a peripheral role or advertiser role -- will not be affected.

However, if there is the vulnerability, the potential attacker can send out multiple benign BLE broadcast messages that are stored on the memory of the chip. If the chip remains powered up, the data remains. It can be later used with an overflow packet to trigger a memory overflow.

The overflow then can be used to remotely execute malicious code.

The APs are that are affected include Cisco's 1542 AP, 1815 AP, 4800 AP, as well as Meraki's MR33, MR30H, MR74 and MR53E, according to Armis.

The second problem (CVE-2018-7080) is a backdoor used by developers to push over-the-air downloads (OAD) of the chip's firmware that has snuck into production devices. It is enabled by a preset password.

Attackers could modify firmware through this, allowing for remote code execution (RCE) and other security problems.

Armis found the backdoor present in Aruba WiFi access point Series 300 systems.

In addition, Armis researchers found that the attacks utilizing Bleedingbit cannot be detected by traditional antivirus tools. However, there are updates to follow:

  • For CVE-2018-16986 mitigation, the TI BLE-STACK update has been released
  • Customers using CC2640 (non-R2) and CC2650 with BLE-STACK version 2.2.1 or earlier should update to version 2.2.2
  • Customers using CC2640R2F, with SimpleLink CC2640R2 SDK version 1.00.00.22 (BLE-STACK 3.0.0) need to update to SimpleLink CC2640R2F SDK version 1.30.00.25 (BLE-STACK 3.0.1) or later
  • Customers using CC1350, with SimpleLink CC13x0 SDK version 2.20.00.38 (BLE-STACK 2.3.3) or earlier will need to update to SimpleLink CC13x0 SDK version 2.30.00.20 (BLE-STACK 2.3.4) or later

However, for the OAD problem, it will depend on manufacturers that have included OAD functionality in their products to rectify it.

This is a chip-level supply chain attack at its root. The chips used in the product have the vulnerability, and the chip is where mitigation efforts must be addressed.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...