LabWiki up to 1.1 edit.php userfile unrestricted upload

Summaryinfo

A vulnerability was found in LabWiki up to 1.1. It has been classified as critical. Affected is an unknown function of the file edit.php. This manipulation of the argument userfile as part of Parameter causes unrestricted upload. This vulnerability is tracked as CVE-2011-4334. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in LabWiki up to 1.1 (Content Management System). It has been declared as critical. Affected by this vulnerability is an unknown code block of the file edit.php. The manipulation of the argument userfile as part of a Parameter leads to a unrestricted upload vulnerability. The CWE definition for the vulnerability is CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

edit.php in LabWiki 1.1 and earlier does not properly verify uploaded user files, which allows remote authenticated users to upload arbitrary PHP files via a PHP file with a .gif extension in the userfile parameter.

The bug was discovered 11/21/2011. The weakness was disclosed 10/23/2017 (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2011-4334 since 11/04/2011. The attack can be launched remotely. The requirement for exploitation is a single authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1608.002 according to MITRE ATT&CK.

It is possible to download the exploit 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 2163 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:edit.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 (18100) and OSVDB (76933†). The entry VDB-108546 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• LabWiki

Version

• 1.0
• 1.1

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