Bookelves Kipper 2.01 default.php configfile path traversal

Summaryinfo

A vulnerability was found in Bookelves Kipper 2.01 and classified as problematic. Affected is an unknown function of the file default.php. Executing a manipulation of the argument configfile can lead to path traversal. This vulnerability is tracked as CVE-2009-0766. Moreover, an exploit is present.

Detailsinfo

A vulnerability has been found in Bookelves Kipper 2.01 and classified as critical. This vulnerability affects an unknown code of the file default.php. The manipulation of the argument configfile 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. CVE summarizes:

Directory traversal vulnerability in default.php in Kipper 2.01 allows remote attackers to include and execute arbitrary local files via directory traversal sequences in the configfile parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The weakness was disclosed 03/06/2009 (Website). The advisory is available at secunia.com. This vulnerability was named CVE-2009-0766 since 03/03/2009. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:default.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 (7993) and Secunia (SA33832†). The entries VDB-47003, VDB-47001, VDB-47000 and VDB-46999 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Bookelves

Name

• Kipper

Version

• 2.01

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion