LiveActive security incident?Get immediate response
CVE Record

CVE-2019-8922: A heap-based buffer overflow was discovered in bluetoothd in BlueZ through 5.48.

A heap-based buffer overflow was discovered in bluetoothd in BlueZ through 5.48. There isn't any check on whether there is enough space in the destination buffer. The function simply appends all data passed to it. The values of all attributes that are requested are appended to the output buffer. There are no size checks whatsoever, resulting in a simple heap overflow if one can craft a request where the response is large enough to overflow the preallocated buffer. This issue exists in service_attr_req gets called by process_request (in sdpd-request.c), which also allocates the response buffer.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-8922 is a memory corruption flaw in BlueZ bluetoothd through 5.48. A nearby attacker could trigger a heap overflow through crafted Bluetooth SDP handling, potentially affecting confidentiality, integrity, and availability. No provided source shows confirmed active exploitation.

Executive priority

Treat this as a high-priority exposure for Bluetooth-enabled Linux or appliance fleets, especially laptops, edge systems, and embedded devices. Prioritize patching or disabling Bluetooth where business use is not required.

Technical view

The flaw is a CWE-787 heap-based buffer overflow in bluetoothd SDP request handling. service_attr_req appends requested attribute values into a preallocated response buffer allocated by process_request without checking available space, allowing an oversized response to overflow heap memory.

Likely exposure

Exposure is most likely on Linux systems, embedded devices, appliances, or storage platforms using vulnerable BlueZ bluetoothd with Bluetooth enabled and reachable by nearby attackers. The bundle does not provide complete CPEs or a full vendor inventory.

Exploitation context

CVSS rates this adjacent-network, low-complexity, unauthenticated, no-user-interaction issue as 8.8 high. The CVE is not listed as KEV in the bundle, and the provided sources do not claim active exploitation.

Researcher notes

The strongest evidence is the CVE description and SSD advisory describing missing bounds checks in SDP response construction. Product enumeration is incomplete in the bundle, so validation should focus on BlueZ version, bluetoothd presence, Bluetooth enablement, and vendor advisories.

Mitigation direction

  • Identify systems running BlueZ bluetoothd through 5.48.
  • Apply BlueZ fixes from your Linux distribution or appliance vendor.
  • Review Debian and NetApp advisories for product-specific update guidance.
  • Disable Bluetooth services or radio access where Bluetooth is unnecessary.
  • Track vendor guidance if your platform is not covered by the provided sources.

Validation and detection

  • Confirm whether affected hosts run BlueZ bluetoothd and the installed package version.
  • Check whether Bluetooth is enabled and operational on in-scope systems.
  • Validate vendor advisory applicability for Debian, NetApp, and other managed platforms.
  • Use vulnerability scanner results as evidence, then confirm against package and vendor data.
  • Document exceptions where Bluetooth is disabled or the product is not affected.
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-787: 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-8922 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2019-8922Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.