Nagios Core before 4.3.3 creates a nagios.lock PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for nagios.lock modification before a root script executes a "kill `cat /pathname/nagios.lock`" command.
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
Link | Tags |
---|---|
https://security.gentoo.org/glsa/201710-20 | third party advisory vendor advisory |
https://github.com/NagiosEnterprises/nagioscore/commit/3baffa78bafebbbdf9f448890ba5a952ea2d73cb | patch vendor advisory |
https://github.com/NagiosEnterprises/nagioscore/commit/1b197346d490df2e2d3b1dcce5ac6134ad0c8752 | patch vendor advisory |
https://github.com/NagiosEnterprises/nagioscore/blob/master/Changelog | release notes vendor advisory |
http://www.securityfocus.com/bid/100403 | vdb entry third party advisory |
https://github.com/NagiosEnterprises/nagioscore/issues/404 | issue tracking vendor advisory |