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.
References
Link | Resource |
---|---|
https://github.com/NagiosEnterprises/nagioscore/issues/404 | Issue Tracking 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 | Third Party Advisory VDB Entry |
https://security.gentoo.org/glsa/201710-20 | Third Party Advisory |
Configurations
Information
Published : 2017-08-23 14:29
Updated : 2019-10-02 17:03
NVD link : CVE-2017-12847
Mitre link : CVE-2017-12847
JSON object : View
CWE
CWE-665
Improper Initialization
Products Affected
nagios
- nagios