ThinkPHP 3.2.4 Mysql.class.php parseKey key sql injection

Summaryinfo

A vulnerability was found in ThinkPHP 3.2.4. It has been rated as critical. The impacted element is the function parseKey of the file Library/Think/Db/Driver/Mysql.class.php. The manipulation of the argument key as part of Parameter leads to sql injection. This vulnerability is referenced as CVE-2018-18529. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in ThinkPHP 3.2.4 and classified as critical. This issue affects the function parseKey of the file Library/Think/Db/Driver/Mysql.class.php. The manipulation of the argument key as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

ThinkPHP 3.2.4 has SQL Injection via the count parameter because the Library/Think/Db/Driver/Mysql.class.php parseKey function mishandles the key variable. NOTE: a backquote character is not required in the attack URI.

The bug was discovered 10/19/2018. The weakness was published 10/19/2018 (Website). The advisory is shared at kingkk.com. The identification of this vulnerability is CVE-2018-18529 since 10/19/2018. 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 are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:Library/Think/Db/Driver/Mysql.class.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.

Similar entry is available at VDB-125826. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• ThinkPHP

Version

• 3.2.4

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