{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-16662 exists.","fix":"No fix has been published for CVE-2019-16662 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16662 is a critical command injection vulnerability in n/a, published on 28 Oct 2019. 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-16662 and fix it if it is affected.\n\nWhat it is: CVE-2019-16662 is a critical command injection vulnerability in n/a, published on 28 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-16662 exists.\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-16662/ (Markdown: https://insights.sbomify.com/CVE-2019-16662/index.md)","id":"CVE-2019-16662","markdown":"https://insights.sbomify.com/CVE-2019-16662/index.md","name":"CVE-2019-16662","record":{"aliases":["GHSA-qcxg-gw47-6c75"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"rConfig network config","requires_auth":"none","summary":"Attackers can execute arbitrary system commands via the rootUname parameter in ajaxServerSettingsChk.php due to lack of input filtering.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rconfig","vendor":"rconfig"}],"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":"An issue was discovered in rConfig 3.9.2. An attacker can directly execute system commands by sending a GET request to ajaxServerSettingsChk.php because the rootUname parameter is passed to the exec function without filtering, which can lead to command execution.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2019-10-28","github_poc":1,"max_poc_stars":13,"metasploit":1,"nuclei":1,"refs":[{"date":"2019-11-10T18:26:25Z","kind":"github_poc","ref":"https://github.com/mhaskar/CVE-2019-16662","stars":13,"title":"The official exploit for rConfig 3.9.2 Pre-auth Remote Code Execution CVE-2019-16662"},{"date":"2019-10-28","kind":"metasploit","ref":"exploit/unix/webapp/rconfig_install_cmd_exec","stars":null,"title":"rConfig install Command Execution"},{"date":"2019-10-29","kind":"exploitdb","ref":"47555","stars":null,"title":"rConfig 3.9.2 - Remote Code Execution"},{"date":"2019-11-08","kind":"exploitdb","ref":"47602","stars":null,"title":"rConfig - install Command Execution (Metasploit)"},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-16662.yaml","stars":null,"title":"rConfig 3.9.2 - Remote Code Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2019-16662","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":7,"next":{"headline":"Command injection in n/a","id":"CVE-2019-16663"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16661"},"products":["n/a"],"published":"2019-10-28","related":[{"cvss_score":8.8,"headline":"rConfig OS Command Injection","id":"CVE-2020-10221","kev_date_added":"2021-11-03","published":"2020-03-08"},{"cvss_score":9.9,"headline":"Command injection in n/a","id":"CVE-2020-15715","kev_date_added":null,"published":"2020-07-28"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-23151","kev_date_added":null,"published":"2021-08-09"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-13638","kev_date_added":null,"published":"2020-11-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-10546","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-10547","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-10548","kev_date_added":null,"published":"2020-06-04"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary system commands via the rootUname parameter in ajaxServerSettingsChk.php due to lack of input filtering.","url":"https://insights.sbomify.com/CVE-2019-16662/"}