Zephyr Bluetooth unchecked packet data results in denial of service

published 2021-05-24 5y ago modified 2026-06-17 4mo ago also EUVD-2020-2534

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits: 0; none known

Zephyr Bluetooth unchecked packet data results in denial of service. Zephyr versions >= v1.14.2, >= v2.2.0 contain Improper Handling of Parameters (CWE-233). For more information, see https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-f6vh-7v4x-8fjp

Is CVE-2020-10069 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD	3.1	6.5	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	3.3	AV:A/AC:L/Au:N/C:N/I:N/A:P

Affected products

zephyrproject-rtos zephyr

Classification

Weakness

CWE-233 Improper Handling of Parameters

References

github.com /zephyrproject-rtos/zephyr/security/advisories/GHSA-f6vh-7v4x-8fjp
third-party-advisory

Sources

CVE List CVE-2020-10069
NVD CVE-2020-10069

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.