{"api_version":"1","generated_at":"2026-04-23T06:44:41+00:00","cve":"CVE-2021-21401","urls":{"html":"https://cve.report/CVE-2021-21401","api":"https://cve.report/api/cve/CVE-2021-21401.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2021-21401","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-21401"},"summary":{"title":"CVE-2021-21401","description":"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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2021-03-23 18:15:00","updated_at":"2021-03-29 14:50:00"},"problem_types":["CWE-763"],"metrics":[],"references":[{"url":"https://github.com/nanopb/nanopb/blob/c9124132a604047d0ef97a09c0e99cd9bed2c818/CHANGELOG.txt#L1","name":"https://github.com/nanopb/nanopb/blob/c9124132a604047d0ef97a09c0e99cd9bed2c818/CHANGELOG.txt#L1","refsource":"MISC","tags":[],"title":"nanopb/CHANGELOG.txt at c9124132a604047d0ef97a09c0e99cd9bed2c818 · nanopb/nanopb · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/nanopb/nanopb/issues/647","name":"https://github.com/nanopb/nanopb/issues/647","refsource":"MISC","tags":[],"title":"Ill-formed oneof message leads to calling free on an arbitrary pointer · Issue #647 · nanopb/nanopb · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-7mv5-5mxh-qg88","name":"https://github.com/nanopb/nanopb/security/advisories/GHSA-7mv5-5mxh-qg88","refsource":"CONFIRM","tags":[],"title":"Invalid free() call with oneofs and PB_ENABLE_MALLOC · Advisory · nanopb/nanopb · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/nanopb/nanopb/commit/e2f0ccf939d9f82931d085acb6df8e9a182a4261","name":"https://github.com/nanopb/nanopb/commit/e2f0ccf939d9f82931d085acb6df8e9a182a4261","refsource":"MISC","tags":[],"title":"Fix invalid free() with oneof (#647) · nanopb/nanopb@e2f0ccf · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-21401","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21401","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2021","cve_id":"21401","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"nanopb_project","cpe5":"nanopb","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2021-21401","qid":"179476","title":"Debian Security Update for nanopb (CVE-2021-21401)"},{"cve":"CVE-2021-21401","qid":"199489","title":"Ubuntu Security Notification for Nanopb Vulnerabilities (USN-6121-1)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2021-21401","STATE":"PUBLIC","TITLE":"Invalid free() call in Nanopb"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"nanopb","version":{"version_data":[{"version_value":">= 0.3.2, <= 0.3.9.7"},{"version_value":">= 0.4.0, <= 0.4.4"}]}}]},"vendor_name":"nanopb"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":7.1,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-763: Release of Invalid Pointer or Reference"}]}]},"references":{"reference_data":[{"name":"https://github.com/nanopb/nanopb/security/advisories/GHSA-7mv5-5mxh-qg88","refsource":"CONFIRM","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-7mv5-5mxh-qg88"},{"name":"https://github.com/nanopb/nanopb/issues/647","refsource":"MISC","url":"https://github.com/nanopb/nanopb/issues/647"},{"name":"https://github.com/nanopb/nanopb/commit/e2f0ccf939d9f82931d085acb6df8e9a182a4261","refsource":"MISC","url":"https://github.com/nanopb/nanopb/commit/e2f0ccf939d9f82931d085acb6df8e9a182a4261"},{"name":"https://github.com/nanopb/nanopb/blob/c9124132a604047d0ef97a09c0e99cd9bed2c818/CHANGELOG.txt#L1","refsource":"MISC","url":"https://github.com/nanopb/nanopb/blob/c9124132a604047d0ef97a09c0e99cd9bed2c818/CHANGELOG.txt#L1"}]},"source":{"advisory":"GHSA-7mv5-5mxh-qg88","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2021-03-23 18:15:00","lastModifiedDate":"2021-03-29 14:50:00","problem_types":["CWE-763"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"LOW","baseScore":7.1,"baseSeverity":"HIGH"},"exploitabilityScore":2.8,"impactScore":4.2},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:S/C:N/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"SINGLE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":5.5},"severity":"MEDIUM","exploitabilityScore":8,"impactScore":4.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*","versionStartIncluding":"0.4.0","versionEndExcluding":"0.4.5","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*","versionEndExcluding":"0.3.9.8","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2021","CveId":"21401","Ordinal":"195527","Title":"CVE-2021-21401","CVE":"CVE-2021-21401","Year":"2021"},"notes":[{"CveYear":"2021","CveId":"21401","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2021","CveId":"21401","Ordinal":"2","NoteData":"2021-03-23","Type":"Other","Title":"Published"},{"CveYear":"2021","CveId":"21401","Ordinal":"3","NoteData":"2021-03-23","Type":"Other","Title":"Modified"}]}}}