{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57078 exists.","fix":"No fix has been published for CVE-2024-57078 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57078 is a high-severity vulnerability in n/a, published on 5 Feb 2025. 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-57078 and fix it if it is affected.\n\nWhat it is: CVE-2024-57078 is a high-severity vulnerability in n/a, published on 5 Feb 2025. 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-57078 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-57078/ (Markdown: https://insights.sbomify.com/CVE-2024-57078/index.md)","id":"CVE-2024-57078","markdown":"https://insights.sbomify.com/CVE-2024-57078/index.md","name":"CVE-2024-57078","record":{"aliases":["GHSA-wqpm-vffm-39w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js utility library","requires_auth":"none","summary":"Prototype pollution in cli-util allows attackers to cause a Denial of Service via crafted payloads, affecting users of this Node.js library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"A prototype pollution in the lib.merge function of cli-util v1.1.27 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.","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":"Other in n/a","id":"CVE-2024-57078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"@zag-js/core prototype pollution","id":"CVE-2024-57079"},"packages":[],"prev":{"headline":"utils-extend Prototype Pollution","id":"CVE-2024-57077"},"products":["n/a"],"published":"2025-02-05","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":"partial"},"state":"PUBLISHED","updated":"2025-02-06","vendors":["n/a"]},"summary":"Prototype pollution in cli-util allows attackers to cause a Denial of Service via crafted payloads, affecting users of this Node.js library.","url":"https://insights.sbomify.com/CVE-2024-57078/"}