{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0304 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2010-0304 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 3 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-0304 and fix it if it is affected.\n\nWhat it is: CVE-2010-0304 is a high-severity memory corruption vulnerability in Wireshark Wireshark, published on 3 Feb 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0304 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-2010-0304/ (Markdown: https://insights.sbomify.com/CVE-2010-0304/index.md)","id":"CVE-2010-0304","markdown":"https://insights.sbomify.com/CVE-2010-0304/index.md","name":"CVE-2010-0304","record":{"aliases":["DEBIAN-CVE-2010-0304","GHSA-jpr3-gg36-wv7f"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Network protocol analyzer","requires_auth":"none","summary":"Remote attackers can crash Wireshark via malformed packets due to buffer overflows in the LWRES dissector, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"wireshark","vendor":"wireshark"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Multiple buffer overflows in the LWRES dissector in Wireshark 0.9.15 through 1.0.10 and 1.2.0 through 1.2.5 allow remote attackers to cause a denial of service (crash) via a malformed packet, as demonstrated using a stack-based buffer overflow to the dissect_getaddrsbyname_request function.","ecosystems":[],"exploits":{"exploitdb":3,"first_seen":"2010-01-27","github_poc":0,"max_poc_stars":null,"metasploit":2,"nuclei":0,"refs":[{"date":"2010-01-27","kind":"metasploit","ref":"exploit/multi/misc/wireshark_lwres_getaddrbyname","stars":null,"title":"Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow"},{"date":"2010-01-27","kind":"metasploit","ref":"exploit/multi/misc/wireshark_lwres_getaddrbyname_loop","stars":null,"title":"Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow (loop)"},{"date":"2010-01-29","kind":"exploitdb","ref":"11288","stars":null,"title":"Wireshark 1.2.5 - 'LWRES getaddrbyname' Stack Buffer Overflow (PoC)"},{"date":"2010-02-11","kind":"exploitdb","ref":"16289","stars":null,"title":"Wireshark - LWRES Dissector getaddrsbyname_request Buffer Overflow (Metasploit)"},{"date":"2010-11-24","kind":"exploitdb","ref":"16292","stars":null,"title":"Wireshark - LWRES Dissector getaddrsbyname_request Buffer Overflow (Loop) (Metasploit)"}],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2010-0304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wireshark:wireshark","products":["wireshark:wireshark"],"type":"memory_corruption","year":"2010"},"n_packages":0,"n_references":18,"next":{"headline":"Denial of service in n/a","id":"CVE-2010-0305"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2010-0303"},"products":["n/a"],"published":"2010-02-03","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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can crash Wireshark via malformed packets due to buffer overflows in the LWRES dissector, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2010-0304/"}