CVE-2020-10061 json
Error handling invalid packet sequence
published 6y ago modified 4mo ago also EUVD-2020-2526
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Improper handling of the full-buffer case in the Zephyr Bluetooth implementation can result in memory corruption. This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions, and version 1.14.0 and later versions.
Patch / fix
- zephyrproject zephyr 1.14.0, 2.2.0
- github.com/zephyrproject-rtos/zephyr#23516 pull request
- github.com/zephyrproject-rtos/zephyr#23517 pull request
- github.com/zephyrproject-rtos/zephyr#23547 pull request
- github.com/zephyrproject-rtos/zephyr#23091 pull request
Is CVE-2020-10061 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 FencerExploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.8 | AV:A/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- zephyrproject-rtos zephyr
Classification
References
-
github.com
/zephyrproject-rtos/zephyr/pull/23516
patch, third-party-advisory
-
github.com
/zephyrproject-rtos/zephyr/pull/23517
patch, third-party-advisory
-
github.com
/zephyrproject-rtos/zephyr/pull/23547
patch, third-party-advisory
-
github.com
/zephyrproject-rtos/zephyr/pull/23091
patch, third-party-advisory
-
docs.zephyrproject.org
/latest/security/vulnerabilities.html#cve-2020-10061
vendor-advisory
-
zephyrprojectsec.atlassian.net
/browse/ZEPSEC-75
third-party-advisory
Sources
- CVE List CVE-2020-10061
- NVD CVE-2020-10061
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.