Mediatheka 4.2 index.php lang path traversal

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Mediatheka 4.2. This vulnerability affects unknown code of the file index.php. The manipulation of the argument lang leads to path traversal. This vulnerability is documented as CVE-2008-5894. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Mediatheka 4.2 and classified as critical. This issue affects an unknown functionality of the file index.php. The manipulation of the argument lang with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Directory traversal vulnerability in index.php in Mediatheka 4.2 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the lang parameter.

The weakness was released 01/12/2009 (Website). It is possible to read the advisory at milw0rm.com. The identification of this vulnerability is CVE-2008-5894 since 01/12/2009. 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. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

A public exploit has been developed by Osirys and been published even before and not after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 29 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 (47349), Exploit-DB (7458), SecurityFocus (BID 32815†) and Secunia (SA33176†). Entry connected to this vulnerability is available at VDB-45852. Statistical analysis made it clear that VulDB provides the best quality 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

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

Discussion