Icinga for Windows certificate can have too-open permissions
Description
The Icinga PowerShell Framework provides configuration and check possibilities to ensure integration and monitoring of Windows environments. In versions prior to 1.13.4, 1.12.4, and 1.11.2, permissions of the Icinga for Windows certificate directory grant every user read access, which results in the exposure of private key of the Icinga certificate for the given host. All installations are affected. Versions 1.13.4, 1.12.4, and 1.11.2 contains a patch. Please note that upgrading to a fixed version of Icinga for Windows will also automatically fix a similar issue present in Icinga 2, CVE-2026-24413. As a workaround, the permissions can be restricted manually by updating the ACL for the given folder C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate (and C:\ProgramData\icinga2\var to fix the issue for the Icinga 2 agent as well) including every sub-folder and item to restrict access for general users, only allowing the Icinga service user and administrators access.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
20.0.1, v1.0.0, v1.0.0-rc2, …+ 1 more
- (no CPE)range: 0.0.1, v1.0.0, v1.0.0-rc2, …
- (no CPE)range: <1.11.2, <1.12.4, <1.13.4
Patches
Vulnerability mechanics
References
3- github.com/Icinga/icinga-powershell-framework/security/advisories/GHSA-88h5-rrm6-5973mitrex_refsource_CONFIRM
- github.com/Icinga/icinga2/security/advisories/GHSA-vfjg-6fpv-4mmrmitrex_refsource_MISC
- icinga.com/blog/releasing-icinga-2-v2-15-2-v2-14-8-v2-13-14-and-icinga-for-windows-v1-13-4-v1-12-4-v1-11-2mitrex_refsource_MISC
News mentions
0No linked articles in our index yet.