Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] Ipswitch WhatsUp Gold WrFreeFormText.asp sUniqueID Parameter Blind SQL Injection

Medium

Synopsis

This vulnerability was reported by Rapid7 and assigned CVE-2015-6004. Rapid7’s blog indicates that CVE-2015-6005 covers the SQL injection, and CVE-2015-6004 covers the XSS, but that doesn’t match what is in the CVE/NVD database. We reached out to CVE to clarify this, who quickly replied that their assignments are based on CERT VU 176160, and do not consider the Rapid7 blog a definitive source. CERT replied saying that was how they assigned and blamed Rapid7 who they would reach out to. Regardless, a new CVE ID is being assigned to this issue in keeping with CVE abstraction policy.

Rapid7’s article indicates that Ipswitch fixed the vulnerability on December 16, 2016. The CVE entry indicates that versions before 16.4 are vulnerable. Finally, Ipswitch even tweeted that they fixed the reported vulnerabilities but did not indicate the fixed version. Since you are reading this advisory, you've probably figured out that this was not fully fixed!

Looking at the WrFreeFormText.asp script, we see the UUID gets appended to an SQL query and executed. This is pretty clearly open for SQL injection abuse. Unfortunately, this is a visually impaired SQL injection (PC term), but we'll allow it. Some examples of exploitation were demonstrated that include displaying the server version and enumerating users. There are very few limits to what an attacker can do and include giving themselves full user rights or changing user names to JavaScript to be executed when the user list is displayed.

Note: That CVE is real! Congrats to the DWF project, a newly minted CNA that operates with transparency and focuses on faster turnaround for CVE assignments. We're their very first assignment. *blush*

Solution

Ipswitch has released version 16.5 to resolve this issue and re-branded the product to WhatsUp Gold 2016.

Disclosure Timeline

2016-02-09 - Issue discovered
2016-02-18 - Mail CVE (cc Rapid7) asking about CVE ID assignment mixup
2016-02-18 - Mail CERT (cc Rapid7) asking about CVE ID assignment mixup
2016-02-18 - CVE replied
2016-02-18 - CERT replied
2016-02-19 - Vendor notified via [email protected] which bounced (LiveChat Specialist fail)
2016-02-19 - Vendor notified via direct contact with WhatsUp developer, obtained via second LiveChat Specialist
2016-03-03 - Vendor replies, fixed in version 16.5 to be released 2016-04-12.
2016-04-26 - Ask vendor if 16.5 was released on schedule
2016-05-03 - Vendor says 16.5 is GA, rebranded What's Up Gold 2016. Requests a draft of our advisory for them to 'approve' before publishing. We send draft.
2016-05-05 - Vendor "isn't sure how to respond", appears displeased with the draft.
2016-05-10 - Vendor requests a call to understand "what will transpire" after posting advisory
2016-05-10 - Tenable tells them how advisory publishing works via email.
2016-05-13 - Vendor requests first paragraph be removed. Tenable assures them it is our complaining about CVE handling, and not theirs.
2016-05-16 - Tenable requests CVE from DWF
2016-05-16 - DWF assigns CVE ID same day.

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]