{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3845 exists.","fix":"No fix has been published for CVE-2006-3845 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3845 is a critical memory corruption vulnerability in n/a, published on 25 Jul 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-3845 and fix it if it is affected.\n\nWhat it is: CVE-2006-3845 is a critical memory corruption vulnerability in n/a, published on 25 Jul 2006. An attacker can exploit it over the internet without logging in, 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-2006-3845 exists.\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-2006-3845/ (Markdown: https://insights.sbomify.com/CVE-2006-3845/index.md)","id":"CVE-2006-3845","markdown":"https://insights.sbomify.com/CVE-2006-3845/index.md","name":"CVE-2006-3845","record":{"aliases":["GHSA-3whr-c946-j943"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WinRAR archive utility","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious LHA archive with a long filename in WinRAR.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winrar","vendor":"rarlab"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Stack-based buffer overflow in lzh.fmt in WinRAR 3.00 through 3.60 beta 6 allows remote attackers to execute arbitrary code via a long filename in a LHA archive.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-07-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-07-18","kind":"exploitdb","ref":"28235","stars":null,"title":"RARLAB WinRAR 3.x - LHA Filename Handling Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2006-3845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"Code injection in n/a","id":"CVE-2006-3846"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-3844"},"products":["n/a"],"published":"2006-07-25","related":[{"cvss_score":7.8,"headline":"RARLAB WinRAR Path Traversal","id":"CVE-2025-6218","kev_date_added":"2025-12-09","published":"2025-06-21"},{"cvss_score":7.8,"headline":"RARLAB WinRAR Code Execution","id":"CVE-2023-38831","kev_date_added":"2023-08-24","published":"2023-08-23"},{"cvss_score":7.8,"headline":"WinRAR Absolute Path Traversal","id":"CVE-2018-20250","kev_date_added":"2022-02-15","published":"2019-02-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-7144","kev_date_added":null,"published":"2009-09-01"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2004-1254","kev_date_added":null,"published":"2004-12-22"},{"cvss_score":7.8,"headline":"RARLAB WinRAR Recovery Volume Improper Validation of Array Index Remote Code Execution Vulnerability","id":"CVE-2023-40477","kev_date_added":null,"published":"2024-05-03"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"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 execute arbitrary code by tricking users into opening a malicious LHA archive with a long filename in WinRAR.","url":"https://insights.sbomify.com/CVE-2006-3845/"}