{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4512 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2023-4512 is a medium-severity denial of service vulnerability in Wireshark Wireshark, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-4512 and fix it if it is affected.\n\nWhat it is: CVE-2023-4512 is a medium-severity denial of service vulnerability in Wireshark Wireshark, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4512 exists.\n\nAffected product: Wireshark Wireshark. 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-2023-4512/ (Markdown: https://insights.sbomify.com/CVE-2023-4512/index.md)","id":"CVE-2023-4512","markdown":"https://insights.sbomify.com/CVE-2023-4512/index.md","name":"CVE-2023-4512","record":{"aliases":["DEBIAN-CVE-2023-4512","GHSA-g65w-25m5-5gcg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Network protocol analyzer","requires_auth":"none","summary":"Attackers can cause Wireshark to crash via crafted packets or files due to uncontrolled recursion in the CBOR dissector.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[{"product":"wireshark","vendor":"wireshark"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"CBOR dissector crash in Wireshark 4.0.0 to 4.0.6 allows denial of service via packet injection or crafted capture file","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Uncontrolled Recursion in Wireshark","id":"CVE-2023-4512","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wireshark:wireshark","products":["wireshark:wireshark"],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Release of Memory after Effective Lifetime in Wireshark","id":"CVE-2023-4513"},"packages":[],"prev":{"headline":"Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark","id":"CVE-2023-4511"},"products":["Wireshark"],"published":"2023-08-24","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2011-0444","kev_date_added":null,"published":"2011-01-12"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-2994","kev_date_added":null,"published":"2010-08-13"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-2995","kev_date_added":null,"published":"2010-08-13"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1266","kev_date_added":null,"published":"2009-04-21"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-1210","kev_date_added":null,"published":"2009-04-01"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-3146","kev_date_added":null,"published":"2008-09-02"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-6112","kev_date_added":null,"published":"2007-11-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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["Wireshark Foundation"]},"summary":"Attackers can cause Wireshark to crash via crafted packets or files due to uncontrolled recursion in the CBOR dissector.","url":"https://insights.sbomify.com/CVE-2023-4512/"}