This change fixes a security related issue n the mk_logwatch 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 logwatch.cfg 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 logwatch.cfg can be written, you should update to the fixed mk_logwatch plugin.
Thanks to Adam Lis for finding and reporting this issue!
What does the attacker need?
He needs to have write access to the /etc/check_mk/logwatch.cfg, 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 logwatch.cfg.
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: