Mediatheka 4.2 connection.php User sql injection

Summaryinfo

A vulnerability, which was classified as critical, was found in Mediatheka 4.2. This issue affects some unknown processing of the file connection.php. The manipulation of the argument User results in sql injection. This vulnerability is reported as CVE-2008-5895. The attack can be launched remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Mediatheka 4.2. It has been classified as critical. Affected is some unknown functionality of the file connection.php. The manipulation of the argument user 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. CVE summarizes:

SQL injection vulnerability in connection.php in Mediatheka 4.2 and earlier allows remote attackers to execute arbitrary SQL commands via the user parameter.

The weakness was disclosed 01/12/2009 (Website). The advisory is shared for download at milw0rm.com. This vulnerability is traded as CVE-2008-5895 since 01/12/2009. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

A public exploit has been developed by StAkeR in Perl and been published even before and not after the advisory. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 28 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:connection.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 (7476), SecurityFocus (BID 32836†) and Secunia (SA33176†). The entry VDB-45851 is pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Mediatheka

Version

• 4.2

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion