rConfig 3.9.2 ajaxServerSettingsChk.php exec rootUname os command injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in rConfig 3.9.2. This vulnerability affects the function exec of the file ajaxServerSettingsChk.php. The manipulation of the argument rootUname as part of System Command leads to os command injection. This vulnerability is uniquely identified as CVE-2019-16662. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in rConfig 3.9.2 and classified as critical. This issue affects the function exec of the file ajaxServerSettingsChk.php. The manipulation of the argument rootUname as part of a System Command leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 10/28/2019 (Website). The advisory is shared at shells.systems. The identification of this vulnerability is CVE-2019-16662 since 09/21/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1202 for this issue.

A public exploit has been developed by mhaskar in Python and been published even before and not after the advisory. The exploit is available at gist.github.com. It is declared as functional. The vulnerability was handled as a non-public zero-day exploit for at least 40 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:ajaxServerSettingsChk.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (47602). The entry VDB-144258 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• rConfig

Version

• 3.9.2

License

• open-source

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion