ezContents 1.4.5 index.php Link path traversal

Summaryinfo

A vulnerability classified as problematic has been found in ezContents 1.4.5. This affects an unknown part of the file index.php. Performing a manipulation of the argument Link results in path traversal. This vulnerability was named CVE-2007-6368. In addition, an exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ezContents 1.4.5. This affects some unknown processing of the file index.php. The manipulation of the argument link with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. The summary by CVE is:

Directory traversal vulnerability in index.php in ezContents 1.4.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the link parameter.

The weakness was presented 12/05/2007 as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-6368 since 12/14/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

After immediately, there has been an exploit disclosed. The exploit is shared for download 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 (4694) and OSVDB (39505†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• ezContents

Version

• 1.4.5

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