{"answers":{"affected":"It affects 22 products.","exploited":"There is no known exploitation of CVE-2022-25368 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25368 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25368 is a medium-severity vulnerability in n/a, published on 9 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-25368 and fix it if it is affected.\n\nWhat it is: CVE-2022-25368 is a medium-severity vulnerability in n/a, published on 9 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-25368 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-2022-25368/ (Markdown: https://insights.sbomify.com/CVE-2022-25368/index.md)","id":"CVE-2022-25368","markdown":"https://insights.sbomify.com/CVE-2022-25368/index.md","name":"CVE-2022-25368","record":{"aliases":["GHSA-5257-57v8-vjc5"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CPU Spectre variant","requires_auth":"low_privilege","summary":"Attackers exploit shared branch history to infer protected information via speculative execution side channels.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ampere_altra_firmware","vendor":"amperecomputing"},{"product":"ampere_altra_max_firmware","vendor":"amperecomputing"},{"product":"cortex-a15_firmware","vendor":"arm"},{"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-a78c_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"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Spectre BHB is a variant of Spectre-v2 in which malicious code uses the shared branch history (stored in the CPU BHB) to influence mispredicted branches in the victim's hardware context. Speculation caused by these mispredicted branches can then potentially be used to cause cache allocation, which can then be used to infer information that should be protected.","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":"Information disclosure in n/a","id":"CVE-2022-25368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-25369"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2022-25366"},"products":["n/a"],"published":"2022-03-09","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-46892","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-32295","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2022-37459","kev_date_added":null,"published":"2022-08-17"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-45454","kev_date_added":null,"published":"2022-08-17"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2022-35888","kev_date_added":null,"published":"2022-09-29"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers exploit shared branch history to infer protected information via speculative execution side channels.","url":"https://insights.sbomify.com/CVE-2022-25368/"}