CVE-2020-10059 json
UpdateHub Module Explicitly Disables TLS Verification
published 6y ago modified 4mo ago also EUVD-2020-2524
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
The UpdateHub module disables DTLS peer checking, which allows for a man in the middle attack. This is mitigated by firmware images requiring valid signatures. However, there is no benefit to using DTLS without the peer checking. See NCC-ZEP-018 This issue affects: zephyrproject-rtos zephyr version 2.1.0 and later versions.
Patch / fix
- github.com/zephyrproject-rtos/zephyr#24954 pull request
- github.com/zephyrproject-rtos/zephyr#24999 pull request
- github.com/zephyrproject-rtos/zephyr#24997 pull request
Is CVE-2020-10059 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
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:N/A:P |
Affected products
- zephyrproject-rtos zephyr
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
github.com
/zephyrproject-rtos/zephyr/pull/24954
patch, third-party-advisory
-
github.com
/zephyrproject-rtos/zephyr/pull/24999
patch, third-party-advisory
-
github.com
/zephyrproject-rtos/zephyr/pull/24997
patch, third-party-advisory
-
zephyrprojectsec.atlassian.net
/browse/ZEPSEC-36
third-party-advisory
- docs.zephyrproject.org /latest/security/vulnerabilities.html#cve-2020-10059
Sources
- CVE List CVE-2020-10059
- NVD CVE-2020-10059
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.