{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25255 exists.","fix":"No fix has been published for CVE-2024-25255 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25255 is a critical command injection vulnerability in n/a, published on 11 Nov 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-25255 and fix it if it is affected.\n\nWhat it is: CVE-2024-25255 is a critical command injection vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25255 exists.\n\nAffected product: n/a. 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-25255/ (Markdown: https://insights.sbomify.com/CVE-2024-25255/index.md)","id":"CVE-2024-25255","markdown":"https://insights.sbomify.com/CVE-2024-25255/index.md","name":"CVE-2024-25255","record":{"aliases":["GHSA-m3m4-wgh9-w3h5"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Sublime Text editor","requires_auth":"none","summary":"Sublime Text 4 allows command injection via the New Build System module, potentially enabling arbitrary code execution, though vendors claim this is intended behavior.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"Sublime Text 4 was discovered to contain a command injection vulnerability via the New Build System module. NOTE: multiple third parties report that this is intended behavior.","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":"Command injection in n/a","id":"CVE-2024-25255","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2024-25260"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-25254"},"products":["n/a"],"published":"2024-11-11","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-24","vendors":["n/a"]},"summary":"Sublime Text 4 allows command injection via the New Build System module, potentially enabling arbitrary code execution, though vendors claim this is intended behavior.","url":"https://insights.sbomify.com/CVE-2024-25255/"}