Checkmk werks level3 August 2014

checkmk-werks-lvl3@lists.checkmk.com

2 participants
2 discussions

Check_MK Werk 1096: New WATO webservices: manage hosts via webinterface

by Andreas Boesl

ID: 1096 Title: New WATO webservices: manage hosts via webinterface Component: WATO Level: 3 Class: New Feature Version: 1.2.5i6 It is now possible to manage hosts via web requests<br> This includes the following operations <ul> <li>Add host</li> <li>Edit host</li> <li>Delete host</li> <li>Get host attributes</li> <li>Host service discovery</li> <li>Activate changes</li> </ul> These operations also work in a distributed environment. You can find more information regarding these web request in the <tt>Roles & Permissions</tt> page under a roles settings. There is a new permission topic <tt>Web API</tt> where you can configure the permission of all available API requests. The help texts for these permissions provide some useful examples. In the near future, there will be a "Howto Web-API" article in our online documentation, too.

9 years, 9 months

Check_MK Werk 0766: Changed transid implemtation to work as CSRF protection (Fixes CVE-2014-2330)

by Lars Michelsen

ID: 0766 Title: Changed transid implemtation to work as CSRF protection (Fixes CVE-2014-2330) Component: Multisite Level: 3 Class: Security Fix Version: 1.2.5i2 This change fixes possible attacks against Check_MK Multisite users. In previous versions a possible attacker could try to make the browsers of authenticated users open URLs of the Check_MK Multisite GUI to execute actions e.g. within WATO without knowledge of the attacked user. To make such an attack possible, there are several things needed: The user must be authenticated with multisite and have enough permission within multisite to execute the actions the attacker wants to use, the attacker needs to know the exact URL to the Multisite GUI. Then the attacker needs to make the user either click on a manipulated link or open a manipulated webpage which makes the browser of the user, where the user is authenticated with multisite, open the URL the attacker wants to make it open. The multisite GUI makes use of transids (transaction ids) when processing form submissions or actions. The transids were mainly used to prevent double execution of actions when reloading the page which performed the action in the browser. Now we changed internal handling of the transid to make it also prevent CSRF attacks. The transid is now some kind of shared secret between the webserver and the browser of the user. This ensures a form submission is intended by a previously requested page. This change impicates an incompatible change: In case you use a script which opens multisite pages to perform an action, e.g. set a downtime and use this with a regular user account which authenticates by username/password, the script won't work anymore after this change. The way to go is to adapt the script and change the user to authenticate with an automation secret instead of a password. For this kind of authentication, you will need to user other URL parameters (_username=... and _secret=...).

9 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Checkmk werks level3 August 2014