{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1751 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1751 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1751 is a medium-severity code injection vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1751 and fix it if it is affected.\n\nWhat it is: CVE-2002-1751 is a medium-severity code injection vulnerability in n/a, published on 21 Jun 2005. 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-2002-1751 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-2002-1751/ (Markdown: https://insights.sbomify.com/CVE-2002-1751/index.md)","id":"CVE-2002-1751","markdown":"https://insights.sbomify.com/CVE-2002-1751/index.md","name":"CVE-2002-1751","record":{"aliases":["GHSA-3j55-q2r8-vc2j"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"csLiveSupport CGI script","requires_auth":"none","summary":"Remote attackers can execute arbitrary Perl code via the setup parameter in csLiveSupport.cgi, leading to full system compromise.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cslivesupport","vendor":"cgiscript.net"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"csLiveSupport.cgi in CGIScript.net csLiveSupport allows remote attackers to execute arbitrary Perl code via the setup parameter, which is processed by the Perl eval function.","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":"Code injection in n/a","id":"CVE-2002-1751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2002-1752"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2002-1750"},"products":["n/a"],"published":"2005-06-21","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 Perl code via the setup parameter in csLiveSupport.cgi, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2002-1751/"}