LiveActive security incident?Get immediate response
CVE Record

CVE-2019-8921: An issue was discovered in bluetoothd in BlueZ through 5.48.

An issue was discovered in bluetoothd in BlueZ through 5.48. The vulnerability lies in the handling of a SVC_ATTR_REQ by the SDP implementation. By crafting a malicious CSTATE, it is possible to trick the server into returning more bytes than the buffer actually holds, resulting in leaking arbitrary heap data. The root cause can be found in the function service_attr_req of sdpd-request.c. The server does not check whether the CSTATE data is the same in consecutive requests, and instead simply trusts that it is the same.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-8921 is a Bluetooth stack information leak in BlueZ bluetoothd through 5.48. A nearby attacker could cause the service to return heap memory beyond the intended buffer, potentially exposing sensitive data. The source bundle does not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat this as a targeted confidentiality risk, not an internet-scale emergency. Prioritize environments where Bluetooth is enabled near untrusted users, including laptops, embedded devices, and appliances. Patch through normal security maintenance unless business context increases adjacent-access risk.

Technical view

The flaw is in BlueZ SDP handling of SVC_ATTR_REQ in service_attr_req within sdpd-request.c. bluetoothd trusts continuation state data across requests instead of verifying it, allowing crafted CSTATE handling to leak arbitrary heap data. CVSS 3.1 is 6.5 with adjacent-network attack vector and high confidentiality impact.

Likely exposure

Exposure is most relevant to Linux, embedded, appliance, or storage environments using BlueZ bluetoothd through 5.48 with Bluetooth SDP reachable to adjacent attackers. The bundle lists affected vendor/product as n/a, so product mapping requires local inventory and vendor advisories.

Exploitation context

The attack vector is adjacent network, with no privileges or user interaction required. The provided sources describe malicious CSTATE handling and heap data leakage, but do not cite public active exploitation or CISA KEV inclusion.

Researcher notes

Evidence supports BlueZ through 5.48 and an SDP continuation-state validation flaw leading to heap disclosure. The source bundle does not provide complete affected product CPEs, fixed upstream version details, or proof of active exploitation, so validation should be inventory-driven and vendor-specific.

Mitigation direction

  • Identify systems running BlueZ bluetoothd through version 5.48.
  • Apply vendor-provided BlueZ security updates, including relevant Debian LTS updates where applicable.
  • Review the NetApp advisory for product-specific exposure and remediation status.
  • Follow operating-system vendor guidance before changing Bluetooth service availability.

Validation and detection

  • Check installed BlueZ package versions against vendor-fixed releases.
  • Confirm whether bluetoothd and SDP functionality are enabled on in-scope systems.
  • Review asset inventory for Linux, embedded, and appliance systems with Bluetooth capability.
  • Verify Debian systems received the DLA 3157-1 bluez security update where applicable.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-8921 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2019-8921Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.