{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4474 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4474 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4474 is a medium-severity memory corruption vulnerability in n/a, published on 22 Dec 2005. 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-4474 and fix it if it is affected.\n\nWhat it is: CVE-2005-4474 is a medium-severity memory corruption vulnerability in n/a, published on 22 Dec 2005. 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: There is no known exploitation of CVE-2005-4474 in the wild and no public exploit code.\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-4474/ (Markdown: https://insights.sbomify.com/CVE-2005-4474/index.md)","id":"CVE-2005-4474","markdown":"https://insights.sbomify.com/CVE-2005-4474/index.md","name":"CVE-2005-4474","record":{"aliases":["GHSA-4482-cr2p-675v"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WinRAR archive utility","requires_auth":"none","summary":"A buffer overflow in WinRAR allows attackers to cause a crash or potentially execute code by tricking users into adding files with specific non-ANSI filenames.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winrar","vendor":"rarlab"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in the \"Add to archive\" command in WinRAR 3.51 allows user-assisted attackers to cause a denial of service (crash) and possibly execute arbitrary code by tricking the user into adding a file whose filename contains a non-default code page and non-ANSI characters, as demonstrated using a Chinese filename, possibly due to buffer expansion when using the WideCharToMultiByte API.  NOTE: it is not clear whether this problem can be exploited for code execution. If not, then perhaps the user-assisted nature of the attack should exclude the issue from inclusion in CVE.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2005-4474","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-4475"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-4473"},"products":["n/a"],"published":"2005-12-22","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"A buffer overflow in WinRAR allows attackers to cause a crash or potentially execute code by tricking users into adding files with specific non-ANSI filenames.","url":"https://insights.sbomify.com/CVE-2005-4474/"}