ThinkPHP 3.2.4 Driver.class.php parseOrder key sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in ThinkPHP 3.2.4. This issue affects the function parseOrder of the file Library/Think/Db/Driver.class.php. This manipulation of the argument key as part of Parameter causes sql injection. This vulnerability appears as CVE-2018-18546. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in ThinkPHP 3.2.4 and classified as critical. Affected by this vulnerability is the function parseOrder of the file Library/Think/Db/Driver.class.php. The manipulation of the argument key as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

ThinkPHP 3.2.4 has SQL Injection via the order parameter because the Library/Think/Db/Driver.class.php parseOrder function mishandles the key variable.

The bug was discovered 10/08/2018. The weakness was presented 10/21/2018 (Website). The advisory is shared at 98587329.github.io. This vulnerability is known as CVE-2018-18546 since 10/20/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

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

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

Productinfo

Name

• ThinkPHP

Version

• 3.2.4

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