IDevSpot iSupport 1.02/1.06/1.8 index.php include_file path traversal

Summaryinfo

A vulnerability was found in IDevSpot iSupport 1.02/1.06/1.8. It has been declared as problematic. Affected by this issue is some unknown functionality of the file index.php. Executing a manipulation of the argument include_file can lead to path traversal. This vulnerability is handled as CVE-2009-4434. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in IDevSpot iSupport 1.02/1.06/1.8. It has been declared as problematic. This vulnerability affects some unknown processing of the file index.php. The manipulation of the argument include_file 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. CVE summarizes:

Directory traversal vulnerability in index.php in IDevSpot iSupport 1.8 and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the include_file parameter.

The weakness was released 12/16/2009 (Website). The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2009-4434 since 12/28/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. The MITRE ATT&CK project declares the attack technique as T1006.

After immediately, there has been an exploit disclosed. It is possible to download the exploit 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 (10478), OSVDB (61110†) and Secunia (SA37726†). Entries connected to this vulnerability are available at VDB-40247 and VDB-51315. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• IDevSpot

Name

• iSupport

Version

• 1.02
• 1.06
• 1.8

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