{"answers":{"affected":"2 open source packages ship an affected version, including curling. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10789 in the wild and no public exploit code.","fix":"Upgrade curling to 1.1.0 or later.","what":"CVE-2019-10789 is a critical command injection vulnerability in curling.js, published on 6 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10789 and fix it if it is affected.\n\nWhat it is: CVE-2019-10789 is a critical command injection vulnerability in curling.js, published on 6 Feb 2020. 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-2019-10789 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- curling (npm): affected all versions; fixed in 1.1.0\n- curling (npm): affected all versions; fixed in 1.1.0\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-2019-10789/ (Markdown: https://insights.sbomify.com/CVE-2019-10789/index.md)","id":"CVE-2019-10789","markdown":"https://insights.sbomify.com/CVE-2019-10789/index.md","name":"CVE-2019-10789","record":{"aliases":["GHSA-xmxh-g7wj-8m4m"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js curling library","requires_auth":"none","summary":"Attackers can execute arbitrary commands via the run function in curling.js due to lack of input sanitization.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"curling","vendor":"curling_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"All versions of curling.js are vulnerable to Command Injection via the run function. The command argument can be controlled by users without any sanitization.","ecosystems":["npm"],"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":"OS Command Injection in curling","id":"CVE-2019-10789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"TaffyDB can allow access to any data items in the DB","id":"CVE-2019-10790"},"packages":[{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"curling","purl":null,"source":"GHSA-xmxh-g7wj-8m4m"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"curling","purl":"pkg:npm/curling","source":"GHSA-xmxh-g7wj-8m4m"}],"prev":{"headline":"OS Command Injection in im-metadata","id":"CVE-2019-10788"},"products":["curling.js"],"published":"2020-02-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via the run function in curling.js due to lack of input sanitization.","url":"https://insights.sbomify.com/CVE-2019-10789/"}