iGaming CMS 2.0 search.php keywords sql injection

Summaryinfo

A vulnerability marked as critical has been reported in iGaming CMS 2.0. Affected by this issue is some unknown functionality of the file search.php. The manipulation of the argument keywords leads to sql injection. This vulnerability is listed as CVE-2008-4603. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in iGaming CMS 2.0 (Content Management System) and classified as critical. This issue affects an unknown code of the file search.php. The manipulation of the argument keywords 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 search.php in iGaming CMS 2.0 Alpha 1 allows remote attackers to execute arbitrary SQL commands via the keywords parameter in a search_games action.

The weakness was presented 10/17/2008 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2008-4603 since 10/17/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 StAkeR in Perl and been published even before and not after the advisory. The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:search.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 (6769) and SecurityFocus (BID 31793†). See VDB-44571 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• iGaming

Name

• CMS

Version

• 2.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