{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5235 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-5235 is a medium-severity memory corruption vulnerability in Nanopb, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5235 and fix it if it is affected.\n\nWhat it is: CVE-2020-5235 is a medium-severity memory corruption vulnerability in Nanopb, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5235 in the wild and no public exploit code.\n\nAffected product: Nanopb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-5235/ (Markdown: https://insights.sbomify.com/CVE-2020-5235/index.md)","id":"CVE-2020-5235","markdown":"https://insights.sbomify.com/CVE-2020-5235/index.md","name":"CVE-2020-5235","record":{"aliases":["GHSA-6f6v-26gj-6crp","GHSA-gcx3-7m76-287p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Nanopb protobuf library","requires_auth":"none","summary":"An out-of-memory condition in Nanopb can lead to crashes or memory corruption when decoding specific repeated fields, potentially allowing code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nanopb","vendor":"nanopb_project"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Out-of-memory condition in Nanopb is potentially exploitable","id":"CVE-2020-5235","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Catastrophic backtracking in regex allows Denial of Service in Waitress","id":"CVE-2020-5236"},"packages":[],"prev":{"headline":"Untrusted data can lead to DoS attack in MessagePack for C# and Unity","id":"CVE-2020-5234"},"products":["Nanopb"],"published":"2020-02-04","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2014-125106","kev_date_added":null,"published":"2023-06-17"},{"cvss_score":7.5,"headline":"Memory leak in nanopb","id":"CVE-2020-26243","kev_date_added":null,"published":"2020-11-25"},{"cvss_score":7.1,"headline":"Invalid free() call in Nanopb","id":"CVE-2021-21401","kev_date_added":null,"published":"2021-03-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["nanopb"]},"summary":"An out-of-memory condition in Nanopb can lead to crashes or memory corruption when decoding specific repeated fields, potentially allowing code execution.","url":"https://insights.sbomify.com/CVE-2020-5235/"}