{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30612 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-30612 is a medium-severity use after free vulnerability in cloud-hypervisor, published on 19 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-30612 and fix it if it is affected.\n\nWhat it is: CVE-2023-30612 is a medium-severity use after free vulnerability in cloud-hypervisor, published on 19 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-30612 in the wild and no public exploit code.\n\nAffected product: cloud-hypervisor. 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-30612/ (Markdown: https://insights.sbomify.com/CVE-2023-30612/index.md)","id":"CVE-2023-30612","markdown":"https://insights.sbomify.com/CVE-2023-30612/index.md","name":"CVE-2023-30612","record":{"aliases":["AZL-26278","GHSA-g6mw-f26h-4jgp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cloud Hypervisor VMM","requires_auth":"high_privilege","summary":"Attackers with write access to the API socket can close arbitrary file descriptors, causing a crash or potential use-after-free in Cloud Hypervisor.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cloud_hypervisor","vendor":"cloudhypervisor"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Cloud hypervisor is a Virtual Machine Monitor for Cloud workloads. This vulnerability allows users to close arbitrary open file descriptors in the Cloud Hypervisor process via sending malicious HTTP request through the HTTP API socket. As a result, the Cloud Hypervisor process can be easily crashed, causing Deny-of-Service (DoS). This can also be a potential Use-After-Free (UAF) vulnerability. Users require to have the write access to the API socket file to trigger this vulnerability.  Impacted versions of Cloud Hypervisor include upstream main branch, v31.0, and v30.0. The vulnerability was initially detected by our `http_api_fuzzer` via oss-fuzz. This issue has been addressed in versions 30.1 and 31.1. Users unable to upgrade may mitigate this issue by ensuring the write access to the API socket file is granted to trusted users only.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Malicious HTTP requests could close arbitrary opening file descriptors in cloud-hypervisor","id":"CVE-2023-30612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Kiwi TCMS unrestricted file upload vulnerability","id":"CVE-2023-30613"},"packages":[],"prev":{"headline":"Reaction metadata exposed in private topics in Discourse-reactions","id":"CVE-2023-30611"},"products":["cloud-hypervisor"],"published":"2023-04-19","related":[{"cvss_score":9.1,"headline":"Cloud Hypervisor: Host File Exfiltration via QCOW Backing File Abuse","id":"CVE-2026-27211","kev_date_added":null,"published":"2026-02-21"}],"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-05","vendors":["cloud-hypervisor"]},"summary":"Attackers with write access to the API socket can close arbitrary file descriptors, causing a crash or potential use-after-free in Cloud Hypervisor.","url":"https://insights.sbomify.com/CVE-2023-30612/"}