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

[R1] Check_MK Multisite Web UI Reflected XSS



The Check_MK Multisite web interface allows administrators to authenticate through webapi.py using the _username and _secret parameters. If authentication through the webapi.py interface fails then an error message is displayed. This error message uses a content type of text/html. The error message takes the following form:

Authentication error: Invalid automation secret for user <username>

Where <username> contains the contents of the _username parameter. This allows an unauthenticated remote attacker to inject arbitrary HTML/Javascript into the failed login message. For example, on an affected target the following URL will create a popup box.



The vendor has released Check_MK version 1.4.0p6 to address this issue.

Disclosure Timeline

2017-06-13 - Issue discovered
2017-06-14 - Disclosed to security at check-mk.org
2017-06-14 - Team at Check_MK confirm vulnerability, introduce fix for next release.
2017-06-20 - Fixed release 1.4.0p6 added to check-mk.org
2017-06-21 - CVE requested / received

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]