{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34635 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34635 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34635 is a critical vulnerability in n/a, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34635 and fix it if it is affected.\n\nWhat it is: CVE-2022-34635 is a critical vulnerability in n/a, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-34635 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-34635/ (Markdown: https://insights.sbomify.com/CVE-2022-34635/index.md)","id":"CVE-2022-34635","markdown":"https://insights.sbomify.com/CVE-2022-34635/index.md","name":"CVE-2022-34635","record":{"aliases":["GHSA-px79-w28w-3h24"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"CVA6 RISC-V core","requires_auth":"none","summary":"The mstatus.sd field fails to update when mstatus.fs is set to Dirty, potentially causing incorrect floating-point state tracking in the CVA6 processor.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cva6","vendor":"openhwgroup"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The mstatus.sd field in CVA6 commit d315ddd0f1be27c1b3f27eb0b8daf471a952299a does not update when the mstatus.fs field is set to Dirty.","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 n/a","id":"CVE-2022-34635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2022-34636"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2022-34634"},"products":["n/a"],"published":"2022-07-18","related":[{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2022-33021","kev_date_added":null,"published":"2022-06-29"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2022-33023","kev_date_added":null,"published":"2022-06-29"},{"cvss_score":5.5,"headline":"Other in n/a","id":"CVE-2022-34633","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2022-34634","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.5,"headline":"Other in n/a","id":"CVE-2022-34636","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.5,"headline":"Other in n/a","id":"CVE-2022-34637","kev_date_added":null,"published":"2022-07-18"}],"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":"The mstatus.sd field fails to update when mstatus.fs is set to Dirty, potentially causing incorrect floating-point state tracking in the CVA6 processor.","url":"https://insights.sbomify.com/CVE-2022-34635/"}