CVE-2020-52356.5MediumCWE-125

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

nanopb · Nanopb

Affected: Nanopb · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.7%probability of exploitation in the next 30 days

77th percentile

050100

Higher than 77% of scored CVEs

6.5MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

nanopb · Nanopb< 0.2.9.4; >= 0.3.0, < 0.3.9.5; >= 0.4.0, < 0.4.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Out-of-bounds Read · Memory Corruption
Vendor: nanopb
Published: February 2020
Band: Possible (1 to 10%), February 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-5235 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.