{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8774 exists.","fix":"No fix has been published for CVE-2025-8774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8774 is a low-severity vulnerability in riscv-boom SonicBOOM, published on 9 Aug 2025. 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-2025-8774 and fix it if it is affected.\n\nWhat it is: CVE-2025-8774 is a low-severity vulnerability in riscv-boom SonicBOOM, published on 9 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8774 exists.\n\nAffected product: riscv-boom SonicBOOM. 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-2025-8774/ (Markdown: https://insights.sbomify.com/CVE-2025-8774/index.md)","id":"CVE-2025-8774","markdown":"https://insights.sbomify.com/CVE-2025-8774/index.md","name":"CVE-2025-8774","record":{"aliases":["GHSA-9j52-q8c5-8mpr"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RISC-V processor core","requires_auth":"low_privilege","summary":"Local attackers can exploit timing discrepancies in the L1 Data Cache to potentially leak sensitive information from the SonicBOOM RISC-V processor.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"risvc-boom","vendor":"boom-core"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"A vulnerability has been found in riscv-boom SonicBOOM up to 2.2.3 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component L1 Data Cache Handler. The manipulation leads to observable timing discrepancy. Local access is required to approach this attack. The complexity of an attack is rather high. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"riscv-boom SonicBOOM L1 Data Cache timing discrepancy","id":"CVE-2025-8774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Qiyuesuo Eelectronic Signature Platform Scheduled Task upload execute unrestricted upload","id":"CVE-2025-8775"},"packages":[],"prev":{"headline":"Dinstar Monitoring Platform 甘肃省危险品库监控平台 login_getPasswordErrorNum.action sql injection","id":"CVE-2025-8773"},"products":["SonicBOOM"],"published":"2025-08-09","related":[{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2022-26296","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":5.5,"headline":"Other in n/a","id":"CVE-2020-29561","kev_date_added":null,"published":"2020-12-04"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-12","vendors":["riscv-boom"]},"summary":"Local attackers can exploit timing discrepancies in the L1 Data Cache to potentially leak sensitive information from the SonicBOOM RISC-V processor.","url":"https://insights.sbomify.com/CVE-2025-8774/"}