phpAbook 0.8.4b/0.8.6b/0.8.7b/0.8.8b config.inc.php path traversal

Summaryinfo

A vulnerability has been found in phpAbook 0.8.4b/0.8.6b/0.8.7b/0.8.8b and classified as problematic. Affected by this issue is some unknown functionality of the file config.inc.php. Performing a manipulation results in path traversal. This vulnerability is reported as CVE-2008-4490. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as problematic has been found in phpAbook 0.8.4b/0.8.6b/0.8.7b/0.8.8b. This affects an unknown part of the file config.inc.php. The manipulation 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, integrity, and availability. The summary by CVE is:

Directory traversal vulnerability in config.inc.php in phpAbook 0.8.8b and earlier, when magic_quotes_gpc is disabled, allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the userInfo cookie.

The weakness was disclosed 10/07/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-4490 since 10/07/2008. The exploitability is told to be difficult. 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.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:config.inc.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 X-Force (45680), Exploit-DB (6679) and SecurityFocus (BID 31581†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• phpAbook

Version

• 0.8.4b
• 0.8.6b
• 0.8.7b
• 0.8.8b

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