{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-2808 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-2808 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-2808 is a medium-severity vulnerability in Google Chrome, published on 6 Nov 2019. 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-2011-2808 and fix it if it is affected.\n\nWhat it is: CVE-2011-2808 is a medium-severity vulnerability in Google Chrome, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2011-2808 in the wild and no public exploit code.\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-2011-2808/ (Markdown: https://insights.sbomify.com/CVE-2011-2808/index.md)","id":"CVE-2011-2808","markdown":"https://insights.sbomify.com/CVE-2011-2808/index.md","name":"CVE-2011-2808","record":{"aliases":["GHSA-7rmf-f3fj-4gh7"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"A stale layout root issue in WebKit allows potential instability or unexpected behavior when accessing keygen elements with autofocus.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"blink","vendor":"google"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A stale layout root is set as an input element in WebKit in Google Chrome before Blink M13 when a child of a keygen with autofocus is accessed.","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":"Other in Chrome","id":"CVE-2011-2808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2011"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2011-2809"},"packages":[],"prev":{"headline":"Other in Chrome","id":"CVE-2011-2807"},"products":["Chrome"],"published":"2019-11-06","related":[{"cvss_score":9.8,"headline":"Integer overflow in Chrome on 64-bit platforms","id":"CVE-2011-2337","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2011-1460","kev_date_added":null,"published":"2019-11-05"},{"cvss_score":7.5,"headline":"Use after free in Chrome","id":"CVE-2011-2335","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2011-1298","kev_date_added":null,"published":"2019-11-06"},{"cvss_score":6.5,"headline":"Memory corruption in Chrome","id":"CVE-2011-1802","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":6.5,"headline":"Use after free in Chrome","id":"CVE-2011-1803","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":6.5,"headline":"Use after free in Chrome","id":"CVE-2011-2334","kev_date_added":null,"published":"2019-11-12"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["Google"]},"summary":"A stale layout root issue in WebKit allows potential instability or unexpected behavior when accessing keygen elements with autofocus.","url":"https://insights.sbomify.com/CVE-2011-2808/"}