{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-31144 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-31144 is a low-severity unsafe deserialization vulnerability in Xen, published on 14 Feb 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-2024-31144 and fix it if it is affected.\n\nWhat it is: CVE-2024-31144 is a low-severity unsafe deserialization vulnerability in Xen, published on 14 Feb 2025. 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-2024-31144 in the wild and no public exploit code.\n\nAffected product: Xen. 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-2024-31144/ (Markdown: https://insights.sbomify.com/CVE-2024-31144/index.md)","id":"CVE-2024-31144","markdown":"https://insights.sbomify.com/CVE-2024-31144/index.md","name":"CVE-2024-31144","record":{"aliases":["GHSA-fg38-pgj3-5w5f","UBUNTU-CVE-2024-31144"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"A malicious guest VM can spoof metadata backups to achieve privilege escalation or code execution on the Xen host during restore operations.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[{"product":"xapi","vendor":"xen"}],"cvss":{"score":3.8,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"For a brief summary of Xapi terminology, see:\n\n   https://xapi-project.github.io/xen-api/overview.html#object-model-overview \n\nXapi contains functionality to backup and restore metadata about Virtual\nMachines and Storage Repositories (SRs).\n\nThe metadata itself is stored in a Virtual Disk Image (VDI) inside an\nSR.  This is used for two purposes; a general backup of metadata\n(e.g. to recover from a host failure if the filer is still good), and\nPortable SRs (e.g. using an external hard drive to move VMs to another\nhost).\n\nMetadata is only restored as an explicit administrator action, but\noccurs in cases where the host has no information about the SR, and must\nlocate the metadata VDI in order to retrieve the metadata.\n\nThe metadata VDI is located by searching (in UUID alphanumeric order)\neach VDI, mounting it, and seeing if there is a suitable metadata file\npresent.  The first matching VDI is deemed to be the metadata VDI, and\nis restored from.\n\nIn the general case, the content of VDIs are controlled by the VM owner,\nand should not be trusted by the host administrator.\n\nA malicious guest can manipulate its disk to appear to be a metadata\nbackup.\n\nA guest cannot choose the UUIDs of its VDIs, but a guest with one disk\nhas a 50% chance of sorting ahead of the legitimate metadata backup.  A\nguest with two disks has a 75% chance, etc.","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":"Xapi: Metadata injection attack against backup/restore functionality","id":"CVE-2024-31144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"error handling in x86 IOMMU identity mapping","id":"CVE-2024-31145"},"packages":[],"prev":{"headline":"double unlock in x86 guest IRQ handling","id":"CVE-2024-31143"},"products":["Xen"],"published":"2025-02-14","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-29487","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":5.3,"headline":"Denial of service in Xapi","id":"CVE-2022-33749","kev_date_added":null,"published":"2022-10-11"}],"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-04-26","vendors":["Xen Project"]},"summary":"A malicious guest VM can spoof metadata backups to achieve privilege escalation or code execution on the Xen host during restore operations.","url":"https://insights.sbomify.com/CVE-2024-31144/"}