{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14935 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14935 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14935 is a critical memory corruption vulnerability in n/a, published on 18 Aug 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-14935 and fix it if it is affected.\n\nWhat it is: CVE-2020-14935 is a critical memory corruption vulnerability in n/a, published on 18 Aug 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-14935 in the wild and no public exploit code.\n\nAffected product: n/a. 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-14935/ (Markdown: https://insights.sbomify.com/CVE-2020-14935/index.md)","id":"CVE-2020-14935","markdown":"https://insights.sbomify.com/CVE-2020-14935/index.md","name":"CVE-2020-14935","record":{"aliases":["GHSA-cvph-4f6c-4mg7"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Contiki-NG IoT OS","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via stack buffer overflow in Contiki-NG's SNMP bulk get request handling.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"contiki-ng","vendor":"contiki-ng"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Buffer overflows were discovered in Contiki-NG 4.4 through 4.5, in the SNMP bulk get request response encoding function. The function parsing the received SNMP request does not verify the input message's requested variables against the capacity of the internal SNMP engine buffer. When a bulk get request response is assembled, a stack buffer dedicated for OIDs (with a limited capacity) is allocated in snmp_engine_get_bulk(). When snmp_engine_get_bulk() is populating the stack buffer, an overflow condition may occur due to lack of input length validation. This makes it possible to overwrite stack regions beyond the allocated buffer, including the return address from the function. As a result, the code execution path may be redirected to an address provided in the SNMP bulk get payload. If the target architecture uses common addressing space for program and data memory, it may also be possible to supply code in the SNMP request payload, and redirect the execution path to the remotely injected code, by modifying the function's return address.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2020-14935","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-14936"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-14934"},"products":["n/a"],"published":"2020-08-18","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2018-19417","kev_date_added":null,"published":"2018-11-21"},{"cvss_score":9.8,"headline":"Contiki-NG has off-by-one error in Antelope DBMS","id":"CVE-2023-30546","kev_date_added":null,"published":"2023-04-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-24336","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-14934","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-14936","kev_date_added":null,"published":"2020-08-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-8359","kev_date_added":null,"published":"2020-04-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":["n/a"]},"summary":"Remote attackers can execute arbitrary code via stack buffer overflow in Contiki-NG's SNMP bulk get request handling.","url":"https://insights.sbomify.com/CVE-2020-14935/"}