{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8799 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8799 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8799 is a critical command injection vulnerability in n/a, published on 5 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8799 and fix it if it is affected.\n\nWhat it is: CVE-2017-8799 is a critical command injection vulnerability in n/a, published on 5 May 2017. 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-2017-8799 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-2017-8799/ (Markdown: https://insights.sbomify.com/CVE-2017-8799/index.md)","id":"CVE-2017-8799","markdown":"https://insights.sbomify.com/CVE-2017-8799/index.md","name":"CVE-2017-8799","record":{"aliases":["GHSA-7525-8gp9-2r6f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"iRODS data management","requires_auth":"none","summary":"Attackers can execute remote shell commands via malicious iRODS virtual pathnames processed by the igetwild Bash script.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"irods","vendor":"irods"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Untrusted input execution via igetwild in all iRODS versions before 4.1.11 and 4.2.1 allows other iRODS users (potentially anonymous) to execute remote shell commands via iRODS virtual pathnames. To exploit this vulnerability, a virtual iRODS pathname that includes a semicolon would be retrieved via igetwild. Because igetwild is a Bash script, the part of the pathname following the semicolon would be executed in the user's shell.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Command injection in n/a","id":"CVE-2017-8799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-8801"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-8798"},"products":["n/a"],"published":"2017-05-05","related":[{"cvss_score":10,"headline":"Multiple unspecified vulnerabilities in iRODS before 3.1 have unknown impact and attack vectors.","id":"CVE-2012-5895","kev_date_added":null,"published":"2012-11-17"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-38462","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2024-38461","kev_date_added":null,"published":"2024-06-16"}],"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":"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-05","vendors":["n/a"]},"summary":"Attackers can execute remote shell commands via malicious iRODS virtual pathnames processed by the igetwild Bash script.","url":"https://insights.sbomify.com/CVE-2017-8799/"}