Easy-scripts Answer/Question Script File Upload myaccount.php memory corruption

Summaryinfo

A vulnerability, which was classified as critical, was found in Easy-scripts Answer and Question Script. Impacted is an unknown function of the file myaccount.php of the component File Upload. Such manipulation leads to memory corruption. This vulnerability is listed as CVE-2009-1663. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in Easy-scripts Answer and Question Script (affected version not known) and classified as critical. Affected by this issue is some unknown functionality of the file myaccount.php of the component File Upload. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Unrestricted file upload vulnerability in myaccount.php in Easy Scripts Answer and Question Script allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in the uploads/[username] directory.

The weakness was presented 05/18/2009 (Website). The advisory is available at milw0rm.com. This vulnerability is handled as CVE-2009-1663 since 05/17/2009. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known.

A public exploit has been developed by InjEctOr5 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 4 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:myaccount.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 vulnerability database at Exploit-DB (8690). See VDB-48220, VDB-48219, VDB-48207 and VDB-48206 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Easy-scripts

Name

• Answer
• Question Script

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion