[checkmk-commits] [tribe29/checkmk] 8fd4db: 14919 SEC Do not log host secret (2)

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 8fd4db3c8c649a1be5e1460af04425137fd4f2f6 https://github.com/tribe29/checkmk/commit/8fd4db3c8c649a1be5e1460af04425137… Author: Maximilian Wirtz &lt;maximilian.wirtz(a)tribe29.com&gt; Date: 2022-10-31 (Mon, 31 Oct 2022) Changed paths: A .werks/14919 Log Message: ----------- 14919 SEC Do not log host secret (2) Unfortunately Werk #14916 was insufficient. Therefore the vulnerability still exists. This Werk fixes the problem. When using the <i>Agent updater</i> the Checkmk server needs a secret in order to allow the agent to download new agents. For security reasons this secret is unique for each host and generated with the <tt>cmk-update-agent register</tt> command. Unfortunately the generated host secret was written to the cmk-update-agent.log. This logfile is not protected and usually world-readable. With this secret one can download the current agent from the Checkmk server. Included in that agent package are the plugin configs which can contain other secrets. (e.g. database credentials) Mitigations without updating: LI: Reregister the agent-updater. Then sanitize the cmk-update-agent.log files. LI: If you cannot rule out that any unauthorized user read <tt>/var/lib/check_mk_agent/cmk-update-agent.log</tt> respectively <tt>C:\ProgramData\checkmk\agent\log\cmk-update-agent.log</tt> you should rotate all secrets that might be or were included in the agent configurations. Steps needed with the update: LI: Update your agent. LI: Reregister the agent-updater. All versions including 1.5 are subject to this vulnerability. We found this vulnerability internally and have no indication of any exploitation. We calculated a CVSS 3.1 score of 6.5 (Medium) with the following vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N Change-Id: I0451ef054f04ca77257ca8d46bd1cb1c6d87acfe