{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9859 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9859 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9859 is a high-severity command injection vulnerability in n/a, published on 10 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9859 and fix it if it is affected.\n\nWhat it is: CVE-2019-9859 is a high-severity command injection vulnerability in n/a, published on 10 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-9859 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-2019-9859/ (Markdown: https://insights.sbomify.com/CVE-2019-9859/index.md)","id":"CVE-2019-9859","markdown":"https://insights.sbomify.com/CVE-2019-9859/index.md","name":"CVE-2019-9859","record":{"aliases":["GHSA-4fq8-68gc-cjqm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Vesta Control Panel","requires_auth":"low_privilege","summary":"Authenticated attackers can achieve remote root access via command injection in VestaCP due to improper use of escapeshellarg.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vesta_control_panel","vendor":"vestacp"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"Vesta Control Panel (VestaCP) 0.9.7 through 0.9.8-23 is vulnerable to an authenticated command execution that can result in remote root access on the server. The platform works with PHP as the frontend language and uses shell scripts to execute system actions. PHP executes shell script through the dangerous command exec. This function can be dangerous if arguments passed to it are not filtered. Every user input in VestaCP that is used as an argument is filtered with the escapeshellarg function. This function comes from the PHP library directly and its description is as follows: \"escapeshellarg() adds single quotes around a string and quotes/escapes any existing single quotes allowing you to pass a string directly to a shell function and having it be treated as a single safe argument.\" It means that if you give Username, it will have 'Username' as a replacement. This works well and protects users from exploiting this potentially dangerous exec function. Unfortunately, VestaCP uses this escapeshellarg function incorrectly in several places.","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-2019-9859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2019-9860"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-9858"},"products":["n/a"],"published":"2020-03-10","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-43693","kev_date_added":null,"published":"2021-11-29"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-1000884","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-10786","kev_date_added":null,"published":"2020-04-21"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-10787","kev_date_added":null,"published":"2020-04-21"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-10808","kev_date_added":null,"published":"2020-03-22"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2021-30462","kev_date_added":null,"published":"2021-04-08"}],"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-04","vendors":["n/a"]},"summary":"Authenticated attackers can achieve remote root access via command injection in VestaCP due to improper use of escapeshellarg.","url":"https://insights.sbomify.com/CVE-2019-9859/"}