Com Fq on Joomla index.php listid sql injection

Summaryinfo

A vulnerability was found in Com Fq on Joomla. It has been classified as critical. The impacted element is an unknown function of the file index.php. Performing a manipulation of the argument listid results in sql injection. This vulnerability was named CVE-2008-0512. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Com Fq on Joomla (Joomla Component) (unknown version). This affects an unknown code block of the file index.php. The manipulation of the argument listid 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 the fq (com_fq) component for Mambo and Joomla! allows remote attackers to execute arbitrary SQL commands via the listid parameter.

The weakness was presented 01/31/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-0512 since 01/31/2008. 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 S@BUN and been published before and not just after the advisory. The exploit is shared for download at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 2 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 X-Force (40035), Exploit-DB (5008) and SecurityFocus (BID 27501†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Joomla Component

Name

• Com Fq

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