{"answers":{"affected":"It affects 22 products.","exploited":"There is no known exploitation of CVE-2022-23960 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-23960 is a medium-severity vulnerability in Debian Debian Linux, published on 12 Mar 2022. 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-2022-23960 and fix it if it is affected.\n\nWhat it is: CVE-2022-23960 is a medium-severity vulnerability in Debian Debian Linux, published on 12 Mar 2022. 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-2022-23960 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-2022-23960/ (Markdown: https://insights.sbomify.com/CVE-2022-23960/index.md)","id":"CVE-2022-23960","markdown":"https://insights.sbomify.com/CVE-2022-23960/index.md","name":"CVE-2022-23960","record":{"aliases":["A-215557547","ALPINE-CVE-2022-23960","ASB-A-215557547","DEBIAN-CVE-2022-23960","GHSA-m7j2-567h-fvrw","UBUNTU-CVE-2022-23960","openSUSE-SU-2024:11935-1"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Arm Cortex processors","requires_auth":"low_privilege","summary":"Attackers can exploit Spectre-BHB in Arm processors to leak sensitive information via branch history buffer speculation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cortex-a57_firmware","vendor":"arm"},{"product":"cortex-a65_firmware","vendor":"arm"},{"product":"cortex-a65ae_firmware","vendor":"arm"},{"product":"cortex-a710_firmware","vendor":"arm"},{"product":"cortex-a72_firmware","vendor":"arm"},{"product":"cortex-a73_firmware","vendor":"arm"},{"product":"cortex-a75_firmware","vendor":"arm"},{"product":"cortex-a76_firmware","vendor":"arm"},{"product":"cortex-a76ae_firmware","vendor":"arm"},{"product":"cortex-a77_firmware","vendor":"arm"},{"product":"cortex-a78_firmware","vendor":"arm"},{"product":"cortex-a78ae_firmware","vendor":"arm"},{"product":"cortex-r7_firmware","vendor":"arm"},{"product":"cortex-r8_firmware","vendor":"arm"},{"product":"cortex-x1_firmware","vendor":"arm"},{"product":"cortex-x2_firmware","vendor":"arm"},{"product":"neoverse-e1_firmware","vendor":"arm"},{"product":"neoverse-v1_firmware","vendor":"arm"},{"product":"neoverse_n1_firmware","vendor":"arm"},{"product":"neoverse_n2_firmware","vendor":"arm"},{"product":"debian_linux","vendor":"debian"},{"product":"xen","vendor":"xen"}],"cvss":{"score":5.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Certain Arm Cortex and Neoverse processors through 2022-03-08 do not properly restrict cache speculation, aka Spectre-BHB. An attacker can leverage the shared branch history in the Branch History Buffer (BHB) to influence mispredicted branches. Then, cache allocation can allow the attacker to obtain sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2022-23960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","xen:xen"],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-23961"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2022-23959"},"products":["n/a"],"published":"2022-03-12","related":[{"cvss_score":5.1,"headline":"Spectre-BSE","id":"CVE-2024-10929","kev_date_added":null,"published":"2025-01-22"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["n/a"]},"summary":"Attackers can exploit Spectre-BHB in Arm processors to leak sensitive information via branch history buffer speculation.","url":"https://insights.sbomify.com/CVE-2022-23960/"}