PHPBasket product.php pro_id sql injection

Summaryinfo

A vulnerability marked as critical has been reported in PHPBasket. This affects an unknown function of the file product.php. The manipulation of the argument pro_id leads to sql injection. This vulnerability is listed as CVE-2008-3713. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in PHPBasket (the affected version is unknown). This issue affects an unknown code of the file product.php. The manipulation of the argument pro_id with an unknown input 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:

SQL injection vulnerability in product.php in PHPBasket allows remote attackers to execute arbitrary SQL commands via the pro_id parameter.

The weakness was presented 08/19/2008 by r45c4l (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2008-3713 since 08/19/2008. 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 T1505 for this issue.

A public exploit has been developed by r45c4l and been published before and not just after the advisory. The exploit is available at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:product.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 databases at X-Force (44524), Exploit-DB (6258) and SecurityFocus (BID 30726†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• PHPBasket

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion