WSN Links 4.0.34p comments.php ID sql injection

Summaryinfo

A vulnerability classified as critical has been found in WSN Links 4.0.34p. This affects an unknown function of the file comments.php. The manipulation of the argument ID leads to sql injection. This vulnerability is documented as CVE-2008-6032. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in WSN Links 4.0.34p. It has been rated as critical. This issue affects some unknown processing of the file comments.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in comments.php in WSN Links Free 4.0.34P allows remote attackers to execute arbitrary SQL commands via the id parameter.

The weakness was released 02/03/2009 (Website). The advisory is shared at milw0rm.com. The identification of this vulnerability is CVE-2008-6032 since 02/02/2009. 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 as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

A public exploit has been developed by Stack and been published before and not just after the advisory. The exploit is available at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 134 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:comments.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 (48534) and Exploit-DB (6529). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• WSN

Name

• Links

Version

• 4.0.34p

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion