Launchpad Ignition 1.2 comment.php blog path traversal

Summaryinfo

A vulnerability described as problematic has been identified in Launchpad Ignition 1.2. This issue affects some unknown processing of the file comment.php. Such manipulation of the argument blog leads to path traversal. This vulnerability is listed as CVE-2009-4426. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in Launchpad Ignition 1.2. It has been rated as critical. Affected by this issue is an unknown code block of the file comment.php. The manipulation of the argument blog 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. CVE summarizes:

Multiple directory traversal vulnerabilities in Ignition 1.2, when magic_quotes_gpc is disabled, allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in the blog parameter to (1) comment.php and (2) view.php.

The weakness was presented 12/20/2009 (Website). The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2009-4426 since 12/28/2009. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1006.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:comment.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 (54940), Exploit-DB (10569), OSVDB (61225†) and Secunia (SA37836†). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Launchpad

Name

• Ignition

Version

• 1.2

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion