{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-47611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47611 is a medium-severity command injection vulnerability in tukaani-project xz, published on 2 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47611 and fix it if it is affected.\n\nWhat it is: CVE-2024-47611 is a medium-severity command injection vulnerability in tukaani-project xz, published on 2 Oct 2024. 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-2024-47611 in the wild and no public exploit code.\n\nAffected product: tukaani-project xz. 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-47611/ (Markdown: https://insights.sbomify.com/CVE-2024-47611/index.md)","id":"CVE-2024-47611","markdown":"https://insights.sbomify.com/CVE-2024-47611/index.md","name":"CVE-2024-47611","record":{"aliases":["GHSA-m538-c5qw-3cg4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"XZ Utils compression library","requires_auth":"none","summary":"Attackers can exploit Unicode filename handling in Windows command-line tools to inject arguments or traverse directories, potentially leading to code execution or data access.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"},{"id":"CWE-176","name":"Improper Handling of Unicode Encoding"}],"description":"XZ Utils provide a general-purpose data-compression library plus command-line tools. When built for native Windows (MinGW-w64 or MSVC), the command line tools from XZ Utils 5.6.2 and older have a command line argument injection vulnerability. If a command line contains Unicode characters (for example, filenames) that don't exist in the current legacy code page, the characters are converted to similar-looking characters with best-fit mapping. Some best-fit mappings result in ASCII characters that change the meaning of the command line, which can be exploited with malicious filenames to do argument injection or directory traversal attacks. This vulnerability is fixed in 5.6.3. Command line tools built for Cygwin or MSYS2 are unaffected. liblzma is unaffected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"XZ Utils on Microsoft Windows platform are vulnerable to argument injection","id":"CVE-2024-47611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"XSS in Special:DataDump when displaying dump status","id":"CVE-2024-47612"},"packages":[],"prev":{"headline":"Stored Cross-site Scripting Vulnerability in Markdown Editor","id":"CVE-2024-47610"},"products":["xz"],"published":"2024-10-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-21","vendors":["tukaani-project"]},"summary":"Attackers can exploit Unicode filename handling in Windows command-line tools to inject arguments or traverse directories, potentially leading to code execution or data access.","url":"https://insights.sbomify.com/CVE-2024-47611/"}