Joomitaly JMovies 1.1 index.php ID sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Joomitaly JMovies 1.1. Impacted is an unknown function of the file index.php. Performing a manipulation of the argument ID results in sql injection. This vulnerability is identified as CVE-2008-5607. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Joomitaly JMovies 1.1. It has been classified as critical. This affects an unknown functionality of the file index.php. The manipulation of the argument id 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 the JMovies (aka JM or com_jmovies) component 1.1 for Joomla! allows remote attackers to execute arbitrary SQL commands via the id parameter to index.php.

The weakness was released 12/16/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-5607 since 12/16/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 in Perl. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. 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 Exploit-DB (7331) and SecurityFocus (BID 32615†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Joomitaly

Name

• JMovies

Version

• 1.1

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