Skip to content

Conversation

@LordHepipud
Copy link
Collaborator

Fixes possible security vulnerability on Icinga for Windows service registration, by not quoting the service path on registration.

You can read more on this on the Knowledge Base Entry with further details, on how to apply the fix and test if you are affected.

Fixes #298

@LordHepipud LordHepipud force-pushed the security/whitespace_in_service_path branch from 6d499ef to 3134689 Compare July 9, 2021 07:22
@LordHepipud LordHepipud force-pushed the security/whitespace_in_service_path branch from 3134689 to 584e3b2 Compare July 9, 2021 07:25
@LordHepipud LordHepipud added this to the v1.5.2 milestone Jul 9, 2021
@LordHepipud LordHepipud added the Security A security flaw within the Icinga PowerShell Framework label Jul 9, 2021
@LordHepipud LordHepipud self-assigned this Jul 9, 2021
@LordHepipud LordHepipud merged commit 25d539e into master Jul 9, 2021
@LordHepipud LordHepipud deleted the security/whitespace_in_service_path branch July 9, 2021 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Security A security flaw within the Icinga PowerShell Framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Microsoft Vulnerability with icinga-service.

2 participants