Customcms CCMS 3.1 index.php skin path traversal

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Customcms CCMS 3.1. This affects an unknown function of the file index.php. This manipulation of the argument skin causes path traversal. This vulnerability is tracked as CVE-2008-4526. Moreover, an exploit is present.

Detailsinfo

A vulnerability has been found in Customcms CCMS 3.1 and classified as critical. Affected by this vulnerability is an unknown functionality of the file index.php. The manipulation of the argument skin with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Multiple directory traversal vulnerabilities in CCMS 3.1 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the skin parameter to (1) index.php, (2) forums.php, (3) admin.php, (4) header.php, (5) pages/story.php and (6) pages/poll.php.

The weakness was disclosed 10/09/2008 by rgod (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2008-4526 since 10/09/2008. 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 T1006 for this issue.

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 (6663) and SecurityFocus (BID 31566†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Customcms

Name

• CCMS

Version

• 3.1

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