{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5370 is a medium-severity vulnerability in Freebsd Freebsd, published on 4 Oct 2023. 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-2023-5370 and fix it if it is affected.\n\nWhat it is: CVE-2023-5370 is a medium-severity vulnerability in Freebsd Freebsd, published on 4 Oct 2023. 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-2023-5370 in the wild and no public exploit code.\n\nAffected product: Freebsd Freebsd. 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-2023-5370/ (Markdown: https://insights.sbomify.com/CVE-2023-5370/index.md)","id":"CVE-2023-5370","markdown":"https://insights.sbomify.com/CVE-2023-5370/index.md","name":"CVE-2023-5370","record":{"aliases":["GHSA-vf42-37cv-443p"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"FreeBSD kernel","requires_auth":"low_privilege","summary":"Attackers can bypass speculative execution protections on CPU 0 in FreeBSD due to initialization order errors, potentially enabling side-channel attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"freebsd","cpe":[{"product":"freebsd","vendor":"freebsd"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"}],"description":"On CPU 0 the check for the SMCCC workaround is called before SMCCC support has been initialized. This resulted in no speculative execution workarounds being installed on CPU 0.","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":"arm64 boot CPUs may lack speculative execution protections","id":"CVE-2023-5370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd"],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory Allocation with Excessive Size Value in Wireshark","id":"CVE-2023-5371"},"packages":[],"prev":{"headline":"copy_file_range insufficient capability rights check","id":"CVE-2023-5369"},"products":["FreeBSD"],"published":"2023-10-04","related":[{"cvss_score":10,"headline":"Memory corruption in FreeBSD","id":"CVE-2018-17160","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-3954","kev_date_added":null,"published":"2014-10-27"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-4304","kev_date_added":null,"published":"2006-08-24"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2006-0226","kev_date_added":null,"published":"2006-01-19"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2004-0002","kev_date_added":null,"published":"2004-02-03"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2001-0969","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2001-0388","kev_date_added":null,"published":"2001-09-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["FreeBSD"]},"summary":"Attackers can bypass speculative execution protections on CPU 0 in FreeBSD due to initialization order errors, potentially enabling side-channel attacks.","url":"https://insights.sbomify.com/CVE-2023-5370/"}