CVE-2018-19860 in Bluetooth firmware

Open
#3,174 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
raspberry-pi
Domain
embedded-iot, security

Research direction

No repository file, test, or entry point is identified in the issue. Review the reproduction project at internalblue, the CVE-2018-19860 report, and the linked Android bulletin; completion would require identifying and applying a fixed Bluetooth firmware for Pi 3B, 3B+, and 4B.

Written by the indexing model from the issue text.

Description

Bluetooth Issue Waiting for internal comment

Is this the right place for my bug report?
I hope it's okay to open this Bluetooth firmware issue here

Describe the bug
Bluetooth firmware does not properly restrict LMP commands and executes certain memory contents upon receiving an LMP command, as demonstrated by executing an HCI command.

To reproduce
Please follow this project:
https://github.com/seemoo-lab/internalblue

System

  • Which model of Raspberry Pi? Pi 3B, 3B+ and 4B

Additional context
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19860

According to this bulletin this issue has been fixed for Android, so there must be a fixed firmware.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.