Webfileexplorer Web File Explorer 3.1 body.asp memory corruption

Summaryinfo

A vulnerability marked as critical has been reported in Webfileexplorer Web File Explorer 3.1. The affected element is an unknown function of the file body.asp. This manipulation of the argument File causes memory corruption. The identification of this vulnerability is CVE-2009-1314. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Webfileexplorer Web File Explorer 3.1. It has been declared as very critical. Affected by this vulnerability is an unknown code of the file body.asp. The manipulation of the argument file with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

body.asp in Web File Explorer 3.1 allows remote attackers to create arbitrary files and execute arbitrary code via the savefile action with a file parameter containing a filename that has an executable extension.

The weakness was shared 04/16/2009 (Website). It is possible to read the advisory at milw0rm.com. This vulnerability is known as CVE-2009-1314 since 04/16/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/26/2024).

A public exploit has been developed by Osirys and been published before and not just after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:body.asp 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 (50389) and Exploit-DB (8382). The entry VDB-47791 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Webfileexplorer

Name

• Web File Explorer

Version

• 3.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