ID: 2320
Title: winperf_msx_queues: no longer crashes in service discovery if there are no msx queues available
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i3
ID: 2372
Title: Avoid freezing WATO during bulk discovery if hosts do not respond in a timely manner
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i3
ID: 2319
Title: winperf_if: fixed exception when using windows_if.ps1 in an old windows version
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i3
The windows_if.ps1 plugin does not provide all informations on windows installations
older than Windows 2003. The winperf_if check was unable to work without the missing data.
This has been fixed.
ID: 2393
Title: Fixed exception "user_confdir" not set in case of exceptions during login
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i3
ID: 2392
Title: Auth cookie is always using "httponly" flag
Component: Multisite
Level: 1
Class: Security Fix
Version: 1.2.7i3
All newly issued authentication cookies have the flag "httponly"
set now. This makes the cookie values inaccessible from scripts
executed in the browser, e.g. from Javascript. This secures the
cookie against some sorts of cookie stealing attempts.
See https://www.owasp.org/index.php/HttpOnly for details.
ID: 2391
Title: Auth cookie is using "secure" flag when HTTPS request detected
Component: Multisite
Level: 1
Class: Security Fix
Version: 1.2.7i3
In previous versions the authentication cookie, which identifies an
authenticated user with the GUI, was never using the "secure" flag.
This means the cookie was sent to the webserver when doing HTTP and
HTTPS requests. In such a situation a user which authenticated using
HTTPS could access the GUI using HTTP and was still authenticated
becaus the browser sends the HTTPS related cookie via HTTP. This is
some kind of security risk since the information which should only
be transported using the encrypted HTTPS requests could be transported
in clear text over the network using HTTP.
The GUI tries now to detect the HTTPS requests. In case a HTTPS
request is detected, the cookies are set with the "secure" flag
which makes the cookies only used via HTTPS.
The HTTPS detection currently checks wether or not the HTTP request
header <tt>X-Forwarded-Proto</tt> is set to <tt>https</tt>.
ID: 2371
Title: appdynamics_memory, appdynamics_sessions, appdynamics_web_container: New checks for AppDynamic
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i3
Check_MK now has a new special agent for monitoring AppDynamics via its REST API. Information
is mapped to your existing monitoring hosts via Piggyback.
ID: 2390
Title: Fixed possible XSS issue on views
Component: Multisite
Level: 1
Class: Security Fix
Version: 1.2.7i3
It was possible to use the view_name variable to inject HTML/Javascript
code into the status GUI views.
ID: 2389
Title: Fixed XSS using the _body_class parameter of views
Component: Multisite
Level: 1
Class: Security Fix
Version: 1.2.7i3
It was possible to use the _body_class parameter of the status GUI views
to inject HTML/Javascript code into the pages.
The _body_class parameter, which was only used for internal purposes, has
totally been removed now.