Permis Com Groups 1.0 index.php ID sql injection

Summaryinfo

A vulnerability marked as critical has been reported in Permis Com Groups 1.0. This vulnerability affects unknown code of the file index.php. This manipulation of the argument ID causes sql injection. The identification of this vulnerability is CVE-2009-2789. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Permis Com Groups 1.0 and classified as critical. Affected by this vulnerability is an unknown code of the file index.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. The summary by CVE is:

SQL injection vulnerability in the Permis (com_groups) component 1.0 for Joomla! allows remote attackers to execute arbitrary SQL commands via the id parameter in a list action to index.php. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The weakness was shared 08/17/2009 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is known as CVE-2009-2789 since 08/17/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

It is declared as highly functional. 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 (52142) and SecurityFocus (BID 35849†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Permis

Name

• Com Groups

Version

• 1.0

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion