taocms up to 2014-05-24 install.php db_name code injection

Summaryinfo

A vulnerability classified as critical has been found in taocms up to 2014-05-24. The impacted element is an unknown function of the file install.php. Performing a manipulation of the argument db_name as part of Parameter results in code injection. This vulnerability is identified as CVE-2019-7720. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in taocms up to 2014-05-24. It has been classified as critical. This affects some unknown processing of the file install.php. The manipulation of the argument db_name as part of a Parameter leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

taocms through 2014-05-24 allows eval injection by placing PHP code in the install.php db_name parameter and then making a config.php request.

The bug was discovered 01/28/2019. The weakness was released 02/11/2019. This vulnerability is uniquely identified as CVE-2019-7720 since 02/10/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:install.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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• taocms

Version

• 2014-05-24

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion