CVE-2021-214017.1HighCWE-763

CVE-2021-21401: Invalid free() call in 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.8%probability of exploitation in the next 30 days

78th percentile

050100

Higher than 78% of scored CVEs

7.1HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

Nanopb is a small code-size Protocol Buffers implementation in ansi C. In Nanopb before versions 0.3.9.8 and 0.4.5, decoding a specifically formed message can cause invalid `free()` or `realloc()` calls if the message type contains an `oneof` field, and the `oneof` directly contains both a pointer field and a non-pointer field. If the message data first contains the non-pointer field and then the pointer field, the data of the non-pointer field is incorrectly treated as if it was a pointer value. Such message data rarely occurs in normal messages, but it is a concern when untrusted data is parsed. This has been fixed in versions 0.3.9.8 and 0.4.5. See referenced GitHub Security Advisory for more information including workarounds.

Affected products1

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

nanopb · nanopb>= 0.3.2, <= 0.3.9.7; >= 0.4.0, <= 0.4.4

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: Release of Invalid Pointer or Reference · Memory Corruption
Vendor: nanopb
Published: March 2021
Band: Possible (1 to 10%), March 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2021-21401 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.