Cms.tut.su CMS Chainuk up to 1.2 Error Message index.php ID information disclosure

Summaryinfo

A vulnerability has been found in Cms.tut.su CMS Chainuk up to 1.2 and classified as problematic. This issue affects some unknown processing of the file index.php of the component Error Message Handler. This manipulation of the argument ID causes information disclosure. This vulnerability is tracked as CVE-2009-2332. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Cms.tut.su CMS Chainuk up to 1.2 (Content Management System). It has been declared as problematic. Affected by this vulnerability is an unknown part of the file index.php of the component Error Message Handler. The manipulation of the argument id with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:

CMS Chainuk 1.2 and earlier allows remote attackers to obtain sensitive information via (1) a crafted id parameter to index.php or (2) a nonexistent folder name in the id parameter to admin/admin_delete.php, which reveals the installation path in an error message.

The weakness was disclosed 07/01/2009 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2009-2332 since 07/05/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. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. 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 Exploit-DB (9069) and OSVDB (55670†). The entries VDB-48878, VDB-48876 and VDB-48875 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• Cms.tut.su

Name

• CMS Chainuk

Version

• 1.0
• 1.1
• 1.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion