{"api_version":"1","generated_at":"2026-04-23T04:52:41+00:00","cve":"CVE-2020-5235","urls":{"html":"https://cve.report/CVE-2020-5235","api":"https://cve.report/api/cve/CVE-2020-5235.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2020-5235","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-5235"},"summary":{"title":"CVE-2020-5235","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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2020-02-04 03:15:00","updated_at":"2020-02-06 18:51:00"},"problem_types":["CWE-125"],"metrics":[],"references":[{"url":"https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3","name":"https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"Fix invalid free() after failed realloc() (GHSA-gcx3-7m76-287p) · nanopb/nanopb@7b39682 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p","name":"https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p","refsource":"CONFIRM","tags":["Patch","Third Party Advisory"],"title":"Out-of-memory condition on repeated field can result in invalid free() · Advisory · nanopb/nanopb · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856","name":"https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"Fix invalid free() after failed realloc() (GHSA-gcx3-7m76-287p) · nanopb/nanopb@45582f1 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2","name":"https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2","refsource":"MISC","tags":["Patch","Third Party Advisory"],"title":"Fix invalid free() after failed realloc() (GHSA-gcx3-7m76-287p) · nanopb/nanopb@aa9d0d1 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-5235","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-5235","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2020","cve_id":"5235","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"nanopb_project","cpe5":"nanopb","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2020","cve_id":"5235","vulnerable":"1","versionEndIncluding":"1","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-2020-5235","qid":"610329","title":"Google Pixel Android April 2021 Security Patch Missing"},{"cve":"CVE-2020-5235","qid":"610347","title":"Google Android May 2021 Security Patch Missing for Huawei EMUI"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2020-5235","STATE":"PUBLIC","TITLE":"Out-of-memory condition in Nanopb is potentially exploitable"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"Nanopb","version":{"version_data":[{"version_value":"< 0.2.9.4"},{"version_value":">= 0.3.0, < 0.3.9.5"},{"version_value":">= 0.4.0, < 0.4.1"}]}}]},"vendor_name":"nanopb"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-125: Out-of-bounds Read"}]}]},"references":{"reference_data":[{"name":"https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p","refsource":"CONFIRM","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-gcx3-7m76-287p"},{"name":"https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856","refsource":"MISC","url":"https://github.com/nanopb/nanopb/commit/45582f1f97f49e2abfdba1463d1e1027682d9856"},{"name":"https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3","refsource":"MISC","url":"https://github.com/nanopb/nanopb/commit/7b396821ddd06df8e39143f16e1dc0a4645b89a3"},{"name":"https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2","refsource":"MISC","url":"https://github.com/nanopb/nanopb/commit/aa9d0d1ca78d6adec3adfeecf3a706c7f9df81f2"}]},"source":{"advisory":"GHSA-gcx3-7m76-287p","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2020-02-04 03:15:00","lastModifiedDate":"2020-02-06 18:51:00","problem_types":["CWE-125"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL"},"exploitabilityScore":3.9,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":7.5},"severity":"HIGH","exploitabilityScore":10,"impactScore":6.4,"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:*:*:*:*:*:*:*:*","versionEndExcluding":"0.2.9.4","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*","versionStartIncluding":"0.3.0","versionEndExcluding":"0.3.9.5","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nanopb_project:nanopb:*:*:*:*:*:*:*:*","versionStartIncluding":"0.4.0","versionEndExcluding":"0.4.1","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2020","CveId":"5235","Ordinal":"165449","Title":"CVE-2020-5235","CVE":"CVE-2020-5235","Year":"2020"},"notes":[{"CveYear":"2020","CveId":"5235","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2020","CveId":"5235","Ordinal":"2","NoteData":"2020-02-03","Type":"Other","Title":"Published"},{"CveYear":"2020","CveId":"5235","Ordinal":"3","NoteData":"2020-02-03","Type":"Other","Title":"Modified"}]}}}