{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4620 exists.","fix":"No fix has been published for CVE-2005-4620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4620 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jan 2006. 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-2005-4620 and fix it if it is affected.\n\nWhat it is: CVE-2005-4620 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jan 2006. 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-2005-4620 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-2005-4620/ (Markdown: https://insights.sbomify.com/CVE-2005-4620/index.md)","id":"CVE-2005-4620","markdown":"https://insights.sbomify.com/CVE-2005-4620/index.md","name":"CVE-2005-4620","record":{"aliases":["GHSA-4cg6-r453-9frw"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WinRAR archive utility","requires_auth":"none","summary":"Local attackers can execute arbitrary code via a buffer overflow in WinRAR triggered by long command-line arguments, requiring user interaction.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winrar","vendor":"rarlab"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in WinRAR 3.50 and earlier allows local users to execute arbitrary code via a long command-line argument.  NOTE: because this program executes with the privileges of the invoking user, and because remote programs do not normally have the ability to specify a command-line argument for this program, there may not be a typical attack vector for the issue that crosses privilege boundaries. Therefore this may not be a vulnerability.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2006-01-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-01-04","kind":"exploitdb","ref":"1403","stars":null,"title":"WinRAR 3.30 - 'Filename' Local Buffer Overflow (1)"},{"date":"2006-01-04","kind":"exploitdb","ref":"1404","stars":null,"title":"WinRAR 3.30 - 'Filename' Local Buffer Overflow (2)"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2005-4620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-4621"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-4619"},"products":["n/a"],"published":"2006-01-06","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":9.3,"headline":"Memory corruption in n/a","id":"CVE-2006-3845","kev_date_added":null,"published":"2006-07-25"},{"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":"Local attackers can execute arbitrary code via a buffer overflow in WinRAR triggered by long command-line arguments, requiring user interaction.","url":"https://insights.sbomify.com/CVE-2005-4620/"}