{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6996 exists.","fix":"No fix has been published for CVE-2008-6996 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-6996 is a medium-severity vulnerability in Google Chrome, published on 18 Aug 2009. 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-2008-6996 and fix it if it is affected.\n\nWhat it is: CVE-2008-6996 is a medium-severity vulnerability in Google Chrome, published on 18 Aug 2009. 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-2008-6996 exists.\n\nAffected product: Google Chrome. 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-2008-6996/ (Markdown: https://insights.sbomify.com/CVE-2008-6996/index.md)","id":"CVE-2008-6996","markdown":"https://insights.sbomify.com/CVE-2008-6996/index.md","name":"CVE-2008-6996","record":{"aliases":["GHSA-pjjf-xfv6-m83w"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["denial_of_service","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome browser","requires_auth":"none","summary":"Chrome fails to prompt before saving executables, allowing attackers to cause disk consumption or facilitate malware execution via malicious URLs.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chrome","vendor":"google"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Google Chrome BETA (0.2.149.27) does not prompt the user before saving an executable file, which makes it easier for remote attackers or malware to cause a denial of service (disk consumption) or exploit other vulnerabilities via a URL that references an executable file, possibly related to the \"ask where to save each file before downloading\" setting.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2008-09-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2008-09-03","kind":"exploitdb","ref":"6355","stars":null,"title":"Google Chrome 0.2.149.27 - Automatic File Download"}],"tier":"weaponised"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2008-6996","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"other","year":"2008"},"n_packages":0,"n_references":13,"next":{"headline":"Denial of service in n/a","id":"CVE-2008-6997"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2008-6995"},"products":["n/a"],"published":"2009-08-18","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"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":"Chrome fails to prompt before saving executables, allowing attackers to cause disk consumption or facilitate malware execution via malicious URLs.","url":"https://insights.sbomify.com/CVE-2008-6996/"}