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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2020-02-04T03:00:18
Updated: 2024-08-04T08:22:09.040Z
Reserved: 2020-01-02T00:00:00
Link: CVE-2020-5235
Vulnrichment
No data.
NVD
Status : Modified
Published: 2020-02-04T03:15:10.657
Modified: 2024-11-21T05:33:44.057
Link: CVE-2020-5235
Redhat
No data.