Jemscripts DownloadControl 1.0 Error Message dc.php dcid sql injection

Summaryinfo

A vulnerability categorized as critical has been discovered in Jemscripts DownloadControl 1.0. The affected element is an unknown function of the file dc.php of the component Error Message Handler. Executing a manipulation of the argument dcid can lead to sql injection. This vulnerability appears as CVE-2006-2552. The attack may be performed from remote. In addition, an exploit is available.

Detailsinfo

A vulnerability has been found in Jemscripts DownloadControl 1.0 and classified as critical. This vulnerability affects an unknown functionality of the file dc.php of the component Error Message Handler. The manipulation of the argument dcid with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality. CVE summarizes:

Jemscripts DownloadControl 1.0 allows remote attackers to obtain sensitive information via an invalid dcid parameter to dc.php, which leaks the pathname in an error message. NOTE: this was originally claimed to be SQL injection, but it is probably resultant from another issue in functions.php.

The weakness was presented 05/19/2006 by luny (Website). The advisory is shared for download at vupen.com. This vulnerability was named CVE-2006-2552 since 05/23/2006. 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 T1505.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:dc.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 (26576), Exploit-DB (27899), SecurityFocus (BID 18041†) and OSVDB (25716†). See VDB-30389 for similar entry. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Jemscripts

Name

• DownloadControl

Version

• 1.0

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