CVE-2020-5235
Nanopb Project Nanopb vulnerability
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.
Affected products
Nanopb. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Nanopb Project Nanopb 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
- github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856 · Patch
- github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3 · Patch
- github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2 · Patch
- github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p · Patch
- nvd.nist.gov/vuln/detail/CVE-2020-5235
- cve.org/CVERecord?id=CVE-2020-5235
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.