ID: 2385
Title: Fixed possible reflected XSS on all GUI pages where users can produce unhandled exceptions
Component: Multisite
Level: 1
Class: Security Fix
Version: 1.2.7i3
On pages where an authenticated user can trigger an exception which is then displayed
to the user as "Internal error" dialog with details about the exception, it was possible
for the user to inject javascript code which was executed in the context of the authenticated
user.
This has been fixed that javascript/html code which is injected is being escaped correctly.
ID: 2384
Title: Prevent user passwords from being visible in webserver log on user creation
Component: WATO
Level: 1
Class: Security Fix
Version: 1.2.7i3
When a user is created using WATO, the set values of the form fields were logged
directly into the webserver access log, because the form of this page used the
GET request method. Users which have access to the log files would be able to
see the initial passwords. If you use an older version of Check_MK it is a good
idea to set the "Change password at next login or access" to force the user
to change his password on first login.
We changed this form to perform a POST request now to prevent these information
being written to the logs.
ID: 2318
Title: windows agent: no longer crashes when a cached plugin has several hundred sections
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i3
The windows agent crashed when a single cached plugin reported several hundred sections.
Cached plugins needs to be postprocessed, which requires additional heap buffer.
The extra heap buffer was set to a too small value. This has been fixed.
ID: 2317
Title: agent_ruckus_spot: new special agent for querying access point statistics via web interface
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i3
This new special agent queries the web interface of a Ruckus Spot service.
It reports access point information for the 2.4 GHz and 5 GHz bands.
For each band the information consists of
<ul>
<li>Number of devices</li>
<li>Number of time drift problems</li>
<li>Number of devices not responding</li>
</ul>
You can configure levels for the <i>time drift</i> and <i>not responding</i> problems.
Without further configuration the check is always OK.