Php-paid4mail paidbanner.php ID sql injection

Summaryinfo

A vulnerability labeled as critical has been found in Php-paid4mail. Affected is an unknown function of the file paidbanner.php. Executing a manipulation of the argument ID can lead to sql injection. The identification of this vulnerability is CVE-2009-2774. The attack may be launched remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Php-paid4mail (Programming Language Software) (the affected version unknown). It has been declared as critical. This vulnerability affects an unknown part of the file paidbanner.php. The manipulation of the argument ID with an unknown input 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. CVE summarizes:

SQL injection vulnerability in paidbanner.php in PHP Paid 4 Mail Script allows remote attackers to execute arbitrary SQL commands via the ID parameter.

The weakness was shared 08/14/2009 (Website). The advisory is shared for download at milw0rm.com. This vulnerability was named CVE-2009-2774 since 08/14/2009. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

A public exploit has been developed by ThE g0bL!N and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 17 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:paidbanner.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 (52641), Exploit-DB (9287) and Secunia (SA35972†). The entry VDB-49443 is related to this item. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Programming Language Software

Name

• Php-paid4mail

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion