CVE-2019-8922 [High] | Out-of-bounds Write in Bluez

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.

EDB-ID	Source	Kind	Published	Link
—	nvd_ref	exploit_tag		Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

—

nvd_ref

exploit_tag

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.07%	1.43%	+1.36%
2	2025-11-21	0.20%	0.07%	-0.14%
3	2025-11-18	—	0.20%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.07%

1.43%

+1.36%

2025-11-21

0.20%

0.07%

-0.14%

2025-11-18

—

0.20%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:A) Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0
5.8	2.0	MEDIUM	`AV:A/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:A) Requires access to an adjacent network segment. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	6.5	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

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

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

8.8

3.1

HIGH

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

Attack vector (AV:A): Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

5.8

2.0

MEDIUM

AV:A/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:A): Requires access to an adjacent network segment.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

6.5

6.4

[email protected]

OS Trackers for CVE-2019-8922

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2019-8922 not yet assigned priority: Debian including 1 source packages (bluez), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-8922
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-8922
`suse`	high	CVE-2019-8922 severity important: SUSE including 17 source package names (bluez, bluez-4.99-0.9.6.1, …), 100 product×package rows across 40 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (40 product lines)): Fixed 86, Known Not Affected 14.	https://www.suse.com/security/cve/CVE-2019-8922/
`ubuntu`	medium	CVE-2019-8922 medium priority: Ubuntu including 1 source packages (bluez), 13 status rows across 13 suites (bionic, focal, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): not-affected 9, released 3, ignored 1.	https://ubuntu.com/security/CVE-2019-8922

Affected software / configurations for CVE-2019-8922

Vendor	Product	Version	Raw CPE
bluez	bluez	<= 5.48	cpe:2.3:a:bluez:bluez::::::::
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*

References for CVE-2019-8922

URL	Tags
https://lists.debian.org/debian-lts-announce/2022/10/msg00026.html	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20211203-0002/	Third Party Advisory
https://ssd-disclosure.com/ssd-advisory-linux-bluez-information-leak-and-heap-overflow/	Exploit Third Party Advisory

URL

CVE-2019-8922

Public exploit references (Exploit-DB) for CVE-2019-8922

Exploit prediction scoring system (EPSS) score for CVE-2019-8922

Common vulnerability scoring system (CVSS) metrics for CVE-2019-8922

Weakness enumeration for CVE-2019-8922

OS Trackers for CVE-2019-8922

Affected software / configurations for CVE-2019-8922

References for CVE-2019-8922