{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17212 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17212 and fix it if it is affected.\n\nWhat it is: CVE-2019-17212 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2019. 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-2019-17212 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-2019-17212/ (Markdown: https://insights.sbomify.com/CVE-2019-17212/index.md)","id":"CVE-2019-17212","markdown":"https://insights.sbomify.com/CVE-2019-17212/index.md","name":"CVE-2019-17212","record":{"aliases":["GHSA-mh95-3gr3-7p2r"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Arm Mbed OS","requires_auth":"none","summary":"Buffer overflows in the CoAP parser allow attackers to execute arbitrary code or cause denial of service via crafted packets.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mbed","vendor":"mbed"}],"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"},{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"Buffer overflows were discovered in the CoAP library in Arm Mbed OS 5.14.0. The CoAP parser is responsible for parsing received CoAP packets. The function sn_coap_parser_options_parse() parses CoAP input linearly using a while loop. Once an option is parsed in a loop, the current point (*packet_data_pptr) is increased correspondingly. The pointer is restricted by the size of the received buffer, as well as by the 0xFF delimiter byte. Inside each while loop, the check of the value of *packet_data_pptr is not strictly enforced. More specifically, inside a loop, *packet_data_pptr could be increased and then dereferenced without checking. Moreover, there are many other functions in the format of sn_coap_parser_****() that do not check whether the pointer is within the bounds of the allocated buffer. All of these lead to heap-based or stack-based buffer overflows, depending on how the CoAP packet buffer is allocated.","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-2019-17212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17213"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2019-17211"},"products":["n/a"],"published":"2019-11-05","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-17211","kev_date_added":null,"published":"2019-11-05"}],"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-05","vendors":["n/a"]},"summary":"Buffer overflows in the CoAP parser allow attackers to execute arbitrary code or cause denial of service via crafted packets.","url":"https://insights.sbomify.com/CVE-2019-17212/"}