{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0849 is a high-severity command injection vulnerability in n/a, published on 22 Nov 2001. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-0849 and fix it if it is affected.\n\nWhat it is: CVE-2001-0849 is a high-severity command injection vulnerability in n/a, published on 22 Nov 2001. 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-2001-0849 in the wild and no public exploit code.\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-2001-0849/ (Markdown: https://insights.sbomify.com/CVE-2001-0849/index.md)","id":"CVE-2001-0849","markdown":"https://insights.sbomify.com/CVE-2001-0849/index.md","name":"CVE-2001-0849","record":{"aliases":["GHSA-93j4-pg2j-49rv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Viralator CGI script","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by exploiting insecure wget calls in the Viralator CGI script.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"viralator","vendor":"duncan_hall"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"viralator CGI script in Viralator 0.9pre1 and earlier allows remote attackers to execute arbitrary code via a URL for a file being downloaded, which is insecurely passed to a call to wget.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2001-0849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2001"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2001-0850"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2001-0848"},"products":["n/a"],"published":"2001-11-22","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by exploiting insecure wget calls in the Viralator CGI script.","url":"https://insights.sbomify.com/CVE-2001-0849/"}