SPHPBlog 0.4.8 Login index.php blog_theme path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in SPHPBlog 0.4.8. This affects an unknown function of the file index.php of the component Login. The manipulation of the argument blog_theme leads to path traversal. This vulnerability is documented as CVE-2006-6033. There is not any exploit available.

Detailsinfo

A vulnerability was found in SPHPBlog 0.4.8. It has been rated as critical. This issue affects some unknown functionality of the file index.php of the component Login. The manipulation of the argument blog_theme with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Multiple directory traversal vulnerabilities in Simple PHP Blog (SPHPBlog), probably 0.4.8, allow remote attackers to read arbitrary files and possibly include arbitrary PHP code via a .. (dot dot) sequence in the blog_theme parameter in (1) index.php, (2) add_cgi.php, (3) add_link.php, (4) login.php, (5) template.php, or (6) contact.php.

The weakness was released 11/21/2006 as not defined posting (Bugtraq). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2006-6033 since 11/21/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

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 vulnerability database at X-Force (30383). Entry connected to this vulnerability is available at VDB-33370. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• SPHPBlog

Version

• 0.4.8

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion