Traffic manipulation via receive-window packet injection
Published Jun 25, 2021 · Updated Aug 3, 2024
Packet injection in Bluetooth Core Specification 4.0 through 5.2 allows physically proximate attackers to control unencrypted LE traffic. The baseband receiver accepts a crafted packet spoofing the Central address during the Peripheral's receive window before the legitimate Central transmits. A successful injection permits traffic modification, suppression, or insertion on unencrypted links; against encrypted links, it can terminate the link but cannot compromise its confidentiality or integrity.
Summary
What happened
Packet injection in Bluetooth Core Specification 4.0 through 5.2 allows physically proximate attackers to control unencrypted LE traffic. The baseband receiver accepts a crafted packet spoofing the Central address during the Peripheral's receive window before the legitimate Central transmits. A successful injection permits traffic modification, suppression, or insertion on unencrypted links; against encrypted links, it can terminate the link but cannot compromise its confidentiality or integrity.
The record
- CVE
- CVE-2021-31615
- Published
- Jun 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo