Vulnerabilities · 2020 · St
CVE-2020-20949
Stm32cubef0 vulnerability
Bleichenbacher's attack on PKCS #1 v1.5 padding for RSA in STM32 cryptographic firmware library software expansion for STM32Cube (UM1924). The vulnerability can allow one to use Bleichenbacher's oracle attack to decrypt an encrypted ciphertext by making successive queries to the server using the vulnerable library, resulting in remote information disclosure.
Affected products
Stm32cubef0, Stm32cubef1, Stm32cubef2, Stm32cubef3, Stm32cubef4, Stm32cubef7, Stm32cubeg0, Stm32cubeg4, Stm32cubeh7, Stm32cubeide and more. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Stm32cubef0 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- archiv.infsec.ethz.ch/education/fs08/secsem/bleichenbacher98.pdf · Third Party Advisory
- bi-zone.medium.com/silence-will-fall-or-how-it-can-take-2-years-to-get-your-vuln-registere · Third Party Advisory
- www.st.com/en/embedded-software/x-cube-cryptolib.html · Third Party Advisory
- st.com
- x-cube-cryptolib.com
- nvd.nist.gov/vuln/detail/CVE-2020-20949
- cve.org/CVERecord?id=CVE-2020-20949
More vulnerabilities in St products
CVE-2024-50597CVE-2024-50596CVE-2024-50595CVE-2024-50594CVE-2024-50385CVE-2024-50384CVE-2024-45064CVE-2023-50096All 29
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.