CVE-2020-15531 json
Silicon Labs Bluetooth Low Energy SDK before 2.13.3 has a buffer overflow via packet data.
published 2020-08-19 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-7518
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Silicon Labs Bluetooth Low Energy SDK before 2.13.3 has a buffer overflow via packet data. This is an over-the-air remote code execution vulnerability in Bluetooth LE in EFR32 SoCs and associated modules running Bluetooth SDK, supporting Central or Observer roles.
Patch / fix
- silabs bluetooth_low_energy_software_development_kit 2.13.3.0
Exploit prediction
3.16% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/darkmentorllc/jackbnimble/blob/master/host/pocs/silabs_efr32_extadv_rce.py referenced PoC, tagged "exploit" by a source, unverified
- youtube.com https://www.youtube.com/watch?v=saoTr1NwdzM referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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 |
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
github.com
/darkmentorllc/jackbnimble/blob/master/host/pocs/silabs_efr32_extadv_rce.py
exploit, third-party-advisory
-
youtube.com
/watch?v=saoTr1NwdzM
exploit, third-party-advisory
-
blackhat.com
/us-20/briefings/schedule/#finding-new-bluetooth-low-energy-exploits-via-reverse-engineering-multiple-vendors-
third-party-advisory
-
github.com
/darkmentorllc/publications/tree/master/2020/TI_SILABS_BLE_RCEs
third-party-advisory
Sources
- CVE List CVE-2020-15531
- NVD CVE-2020-15531
Fencer Vulns 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.