{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23005 exists.","fix":"No fix has been published for CVE-2022-23005 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23005 is a high-severity vulnerability in NA, published on 23 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23005 and fix it if it is affected.\n\nWhat it is: CVE-2022-23005 is a high-severity vulnerability in NA, published on 23 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23005 exists.\n\nAffected product: NA. 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-23005/ (Markdown: https://insights.sbomify.com/CVE-2022-23005/index.md)","id":"CVE-2022-23005","markdown":"https://insights.sbomify.com/CVE-2022-23005/index.md","name":"CVE-2022-23005","record":{"aliases":["GHSA-r8q9-q4r9-jj89"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"UFS Host Boot ROM","requires_auth":"high_privilege","summary":"Attackers can disable boot capability or revert to old boot loader code if UFS Host Boot ROM is improperly implemented.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WDC PSIRT","cpe":[{"product":"universal_flash_storage","vendor":"jedec"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-662","name":"Improper Synchronization"},{"id":"CWE-1262","name":"Improper Access Control for Register Interface"},{"id":"CWE-1233","name":"Security-Sensitive Hardware Controls with Missing Lock Bit Protection"},{"id":"CWE-1224","name":"Improper Restriction of Write-Once Bit Fields"}],"description":"Western Digital has identified a weakness in the UFS standard that could result in a security vulnerability. This vulnerability may exist in some systems where the Host boot ROM code implements the UFS Boot feature to boot from UFS compliant storage devices. The UFS Boot feature, as specified in the UFS standard, is provided by UFS devices to support platforms that need to download the system boot loader from external non-volatile storage locations. Several scenarios have been identified in which adversaries may disable the boot capability, or revert to an old boot loader code, if the host boot ROM code is improperly implemented. UFS Host Boot ROM implementers may be impacted by this vulnerability. UFS devices are only impacted when connected to a vulnerable UFS Host and are not independently impacted by this vulnerability. When present, the vulnerability is in the UFS Host implementation and is not a vulnerability in Western Digital UFS Devices. Western Digital has provided details of the vulnerability to the JEDEC standards body, multiple vendors of host processors, and software solutions providers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Host Boot ROM Code Vulnerability in Systems Implementing UFS Boot Feature","id":"CVE-2022-23005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Buffer Overflow Vulnerability in Western Digital My Cloud Home Products and SanDisk ibi","id":"CVE-2022-23006"},"packages":[],"prev":{"headline":"Algorithm incorrectly returning error and Invalid unreduced value written to output buffer","id":"CVE-2022-23004"},"products":["NA"],"published":"2023-01-23","related":[],"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-04-01","vendors":["NA"]},"summary":"Attackers can disable boot capability or revert to old boot loader code if UFS Host Boot ROM is improperly implemented.","url":"https://insights.sbomify.com/CVE-2022-23005/"}