Frankmancuso Auth Php 1.0 login.php sql injection

Summaryinfo

A vulnerability was found in Frankmancuso Auth Php 1.0. It has been rated as critical. This impacts an unknown function of the file login.php. The manipulation leads to sql injection. This vulnerability is documented as CVE-2009-0738. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Frankmancuso Auth Php 1.0 (Programming Language Software). It has been rated as critical. This issue affects an unknown function of the file login.php. The manipulation 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 login.php in Auth Php 1.0 allows remote attackers to execute arbitrary SQL commands via the (1) username and (2) passwd parameters.

The weakness was released 02/25/2009 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2009-0738 since 02/25/2009. 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 x0r and been published even before and not after the advisory. The exploit is available 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 15 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:login.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 (8033), SecurityFocus (BID 33723†) and Secunia (SA33908†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• Frankmancuso

Name

• Auth Php

Version

• 1.0

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