Log in Start free

Vulnerability · Published Feb 4, 2020 · Assigned by GitHub_M

CVE-2020-5235Out-of-memory condition in Nanopb is potentially exploitable

Medium 6.5

In plain English

A medium-severity out-of-bounds read in Nanopb from nanopb. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.7% (higher than 78% of all known vulnerabilities).

Severity (CVSS 3.1)6.5Medium
Exploit odds (30 days)1.7%top 22.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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 (as reported)

VendorProductVersions
nanopb Nanopb < 0.2.9.4>= 0.3.0, < 0.3.9.5>= 0.4.0, < 0.4.1

Weakness: CWE-125 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

References