Advisory Details

August 7th, 2017

(0Day) Advantech WebAccess ExlViewer getTemplateDetailByName template SQL Injection Information Disclosure Vulnerability

ZDI-17-524
ZDI-CAN-4211

CVE ID
CVSS SCORE 5, (AV:N/AC:L/Au:N/C:P/I:N/A:N)
AFFECTED VENDORS Advantech
AFFECTED PRODUCTS WebAccess
TREND MICRO CUSTOMER PROTECTION Trend Micro TippingPoint IPS customers are protected against this vulnerability by Digital Vaccine protection filter ID 25848. For further product information on the TippingPoint IPS: http://www.tippingpoint.com
VULNERABILITY DETAILS


This vulnerability allows remote attackers to disclose sensitive information on vulnerable installations of Advantech WebAccess. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within ExlViewer.dll. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to extract information from the underlying database.

ADDITIONAL DETAILS


This vulnerability is being disclosed publicly without a patch in accordance with the ZDI 120 day deadline.

11/08/2016, 11/09/2016, 11/10/2016 and 11/15/2016 - ZDI disclosed the reports, 44 in all, to ICS-CERT
11/09/2016 - The vendor acknowledged receipt of the report through ICS-CERT and ICS-CERT provided ICS-VU-714103
04/27/2017 - ICS-CERT notified ZDI these might be fixed in the latest version and asked would ZDI re-test
05/03/2017 - ZDI replied that we cannot do the testing for Advantech
ICS-CERT did not respond
06/23/2017 - ZDI wrote to ICS-CERT requesting any available update
07/31/2017 - ZDI wrote to ICS-CERT requesting any available update
08/01/2017 - ZDI wrote to ICS-CERT advising of the intent to 0-day

-- Mitigation:
Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the service to trusted machines. Only the clients and servers that have a legitimate procedural relationship with the service should be permitted to communicate with it. This could be accomplished in a number of ways, most notably with firewall rules/whitelisting. These features are available in the native Windows Firewall, as described in http://technet.microsoft.com/en-us/library/cc725770%28WS.10%29.aspx and numerous other Microsoft Knowledge Base articles.


DISCLOSURE TIMELINE
  • 2016-11-10 - Vulnerability reported to vendor
  • 2017-08-07 - Coordinated public release of advisory
CREDIT rgod
BACK TO ADVISORIES