{"answers":{"affected":"3 open source packages ship an affected version, including coapthon and CoAPthon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12680 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12680 is a high-severity unsafe deserialization vulnerability in n/a, published on 2 Apr 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-2018-12680 and fix it if it is affected.\n\nWhat it is: CVE-2018-12680 is a high-severity unsafe deserialization vulnerability in n/a, published on 2 Apr 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-2018-12680 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- coapthon (PyPI): affected all versions up to 4.0.2; no fix listed\n- coapthon (PyPI): affected from 3.1; no fix listed\n- CoAPthon (PyPI): affected all versions up to 4.0.2; no fix listed\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-2018-12680/ (Markdown: https://insights.sbomify.com/CVE-2018-12680/index.md)","id":"CVE-2018-12680","markdown":"https://insights.sbomify.com/CVE-2018-12680/index.md","name":"CVE-2018-12680","record":{"aliases":["GHSA-5xc6-fpc7-4qvg","PYSEC-2019-165"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"CoAPthon Python library","requires_auth":"none","summary":"Attackers can cause denial of service in CoAPthon applications by sending crafted CoAP messages that trigger mishandled exceptions during deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"coapthon","vendor":"coapthon_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Serialize.deserialize() method in CoAPthon 3.1, 4.0.0, 4.0.1, and 4.0.2 mishandles certain exceptions, leading to a denial of service in applications that use this library (e.g., the standard CoAP server, CoAP client, CoAP reverse proxy, example collect CoAP server and client) when they receive crafted CoAP messages.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CoAPthon DoS due to Exceptions","id":"CVE-2018-12680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2018"},"n_packages":3,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-12684"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["4.0.2"],"package":"CoAPthon","purl":null,"source":"GHSA-5xc6-fpc7-4qvg"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["4.0.2"],"package":"coapthon","purl":"pkg:pypi/coapthon","source":"GHSA-5xc6-fpc7-4qvg"},{"ecosystem":"PyPI","fixed":[],"introduced":["3.1"],"last_affected":[],"package":"coapthon","purl":"pkg:pypi/coapthon","source":"PYSEC-2019-165"}],"prev":{"headline":"CoAPthon3 vulnerable to Deserialization of Untrusted Data","id":"CVE-2018-12679"},"products":["n/a"],"published":"2019-04-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"Attackers can cause denial of service in CoAPthon applications by sending crafted CoAP messages that trigger mishandled exceptions during deserialization.","url":"https://insights.sbomify.com/CVE-2018-12680/"}