Dieselscripts Diesel Pay index.php sql injection

Summaryinfo

A vulnerability identified as critical has been detected in Dieselscripts Diesel Pay. This impacts an unknown function of the file index.php. Performing a manipulation results in sql injection. This vulnerability was named CVE-2008-6468. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in Dieselscripts Diesel Pay (affected version not known). This affects some unknown functionality of the file index.php. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in index.php in Diesel Pay allows remote attackers to execute arbitrary SQL commands via the area parameter in a browse action.

The weakness was presented 03/13/2009 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2008-6468 since 03/13/2009. 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 and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

A public exploit has been developed by ZoRLu and been published even before and not after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 174 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:index.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 Exploit-DB (6502) and SecurityFocus (BID 31276†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Dieselscripts

Name

• Diesel Pay

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