{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1254 exists.","fix":"No fix has been published for CVE-2004-1254 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-1254 is a critical vulnerability in n/a, published on 22 Dec 2004. 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-2004-1254 and fix it if it is affected.\n\nWhat it is: CVE-2004-1254 is a critical vulnerability in n/a, published on 22 Dec 2004. 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-2004-1254 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-2004-1254/ (Markdown: https://insights.sbomify.com/CVE-2004-1254/index.md)","id":"CVE-2004-1254","markdown":"https://insights.sbomify.com/CVE-2004-1254/index.md","name":"CVE-2004-1254","record":{"aliases":["GHSA-cvq2-4mh6-ww77"],"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 ZIP file with a long filename, causing an integer overflow.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winrar","vendor":"rarlab"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"WinRAR 3.40, and possibly earlier versions, allows remote attackers to execute arbitrary code via a ZIP file containing a file with a long filename, possibly causing an integer overflow that leads to a buffer overflow.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-12-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-12-16","kind":"exploitdb","ref":"694","stars":null,"title":"WinRAR 3.4.1 - Corrupt '.ZIP' File"}],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in n/a","id":"CVE-2004-1254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2004"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2004-1255"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2004-1244"},"products":["n/a"],"published":"2004-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":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-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a malicious ZIP file with a long filename, causing an integer overflow.","url":"https://insights.sbomify.com/CVE-2004-1254/"}