| CVE-2020-5235 | Date: (C)2020-02-04 (M)2023-12-22 |
There is a potentially exploitable out of memory condition In Nanopb before 0.4.1, 0.3.9.5, and 0.2.9.4. When nanopb is compiled with PB_ENABLE_MALLOC, the message to be decoded contains a repeated string, bytes or message field and realloc() runs out of memory when expanding the array nanopb can end up calling `free()` on a pointer value that comes from uninitialized memory. Depending on platform this can result in a crash or further memory corruption, which may be exploitable in some cases. This problem is fixed in nanopb-0.4.1, nanopb-0.3.9.5, nanopb-0.2.9.4.
CVSS Score and Metrics +CVSS Score and Metrics -| CVSS V3 Severity: | CVSS V2 Severity: |
| CVSS Score : 9.8 | CVSS Score : 7.5 |
| Exploit Score: 3.9 | Exploit Score: 10.0 |
| Impact Score: 5.9 | Impact Score: 6.4 |
| |
| CVSS V3 Metrics: | CVSS V2 Metrics: |
| Attack Vector: NETWORK | Access Vector: NETWORK |
| Attack Complexity: LOW | Access Complexity: LOW |
| Privileges Required: NONE | Authentication: NONE |
| User Interaction: NONE | Confidentiality: PARTIAL |
| Scope: UNCHANGED | Integrity: PARTIAL |
| Confidentiality: HIGH | Availability: PARTIAL |
| Integrity: HIGH | |
| Availability: HIGH | |
| | |
