Limbo CMS 1.0.4.2 class_auth.php cookie sql injection

Summaryinfo

A vulnerability classified as critical has been found in Limbo CMS 1.0.4.2. This affects an unknown function of the file class_auth.php. This manipulation of the argument cookie causes sql injection. This vulnerability is registered as CVE-2008-0734. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Limbo CMS 1.0.4.2 (Content Management System). Affected by this vulnerability is some unknown processing of the file class_auth.php. The manipulation of the argument cookie 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. The summary by CVE is:

SQL injection vulnerability in class_auth.php in Limbo CMS 1.0.4.2, and possibly earlier versions, allows remote attackers to execute arbitrary SQL commands via the cuid cookie parameter to admin.php.

The weakness was published 02/12/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2008-0734 since 02/12/2008. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

A public exploit has been developed by The:Paradox in Python and been published before and not just after the advisory. It is possible to download the exploit at securityfocus.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:class_auth.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 (40415), Exploit-DB (5088) and SecurityFocus (BID 27710†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Name

• Limbo CMS

Version

• 1.0.4.2

License

• open-source

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