{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-7096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2008-7096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-7096 is a medium-severity vulnerability in n/a, published on 27 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-7096 and fix it if it is affected.\n\nWhat it is: CVE-2008-7096 is a medium-severity vulnerability in n/a, published on 27 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2008-7096 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-2008-7096/ (Markdown: https://insights.sbomify.com/CVE-2008-7096/index.md)","id":"CVE-2008-7096","markdown":"https://insights.sbomify.com/CVE-2008-7096/index.md","name":"CVE-2008-7096","record":{"aliases":["GHSA-j6vc-v42r-phc6"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Intel BIOS firmware","requires_auth":"high_privilege","summary":"Local administrators with ring 0 privileges can escalate privileges to modify System Management Mode code or access hypervisory memory in Intel BIOS firmware.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bios","vendor":"intel"}],"cvss":{"score":6.9,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Intel Desktop and Intel Mobile Boards with BIOS firmware DQ35JO, DQ35MP, DP35DP, DG33FB, DG33BU, DG33TL, MGM965TW, D945GCPE, and DX38BT allows local administrators with ring 0 privileges to gain additional privileges and modify code that is running in System Management Mode, or access hypervisory memory as demonstrated at Black Hat 2008 by accessing certain remapping registers in Xen 3.3.","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":"Privilege escalation in n/a","id":"CVE-2008-7096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2008"},"n_packages":0,"n_references":7,"next":{"headline":"SQL injection in n/a","id":"CVE-2008-7097"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2008-7095"},"products":["n/a"],"published":"2009-08-27","related":[{"cvss_score":8,"headline":"Memory corruption in Intel BIOS","id":"CVE-2019-14557","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":7.8,"headline":"Memory corruption in Intel(R) Processors","id":"CVE-2020-12360","kev_date_added":null,"published":"2021-06-09"},{"cvss_score":7.8,"headline":"Memory corruption in Intel BIOS Advisory","id":"CVE-2020-8672","kev_date_added":null,"published":"2021-02-02"},{"cvss_score":7.8,"headline":"Privilege escalation in Intel BIOS platform sample code for some Intel(R) Processors","id":"CVE-2020-8739","kev_date_added":null,"published":"2020-11-12"},{"cvss_score":6.8,"headline":"Privilege escalation in Intel(R) Processors","id":"CVE-2020-12359","kev_date_added":null,"published":"2021-06-09"},{"cvss_score":6.7,"headline":"Privilege escalation in Intel(R) Processors","id":"CVE-2020-12357","kev_date_added":null,"published":"2021-06-09"}],"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-07","vendors":["n/a"]},"summary":"Local administrators with ring 0 privileges can escalate privileges to modify System Management Mode code or access hypervisory memory in Intel BIOS firmware.","url":"https://insights.sbomify.com/CVE-2008-7096/"}