Checkmk werks security May 2015

checkmk-werks-sec@lists.checkmk.com

1 participants
1 discussions

Check_MK Werk 2252: mk_logwatch: Fixed mostly uncritical command injection from config

by Lars Michelsen

ID: 2252 Title: mk_logwatch: Fixed mostly uncritical command injection from config Component: Checks & Agents Level: 1 Class: Security Fix Version: 1.2.7i1 This change fixes a security related issue n the <tt>mk_logwatch</tt> linux agent plugin. It was possible to inject commands to the agent plugin when having write access to the logwatch.cfg configuration file. This might result in privilege escalation issues in very rare conditions. >From our point of view this is a low impact issue for nearly all installations out there. Most installations run the agent as root but also have the <tt>logwatch.cfg</tt> only being writable by root. So if a user has write access to this file the user don't need to do privilege escalation anymore since he is already root. If you have the situation where the agent is executed in another user context than the configuration file <tt>logwatch.cfg</tt> can be written, you should update to the fixed <tt>mk_logwatch</tt> plugin. Short Q/As: What does the attacker need? He needs to have write access to the <tt>/etc/check_mk/logwatch.cfg</tt>, which is normally only writable by root. What does the attacker get? He can execute commands in context of the Check_MK-Agent (often root). Do I need to update asap? Only if non-root users can edit the <tt>logwatch.cfg</tt>. I want to update, where can I get the fixed version? If we did not release an updated version yet, you can get it from the git: http://git.mathias-kettner.de/git/?p=check_mk.git;a=blob_plain;f=agents/plu…

9 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Checkmk werks security May 2015