First published: Wed Aug 23 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Nagios | <=4.3.2 |
https://github.com/NagiosEnterprises/nagioscore/commit/1b197346d490df2e2d3b1dcce5ac6134ad0c8752
https://github.com/NagiosEnterprises/nagioscore/commit/3baffa78bafebbbdf9f448890ba5a952ea2d73cb
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-12847 has a medium severity rating due to the potential for local privilege escalation.
To fix CVE-2017-12847, upgrade to Nagios Core version 4.3.3 or later.
CVE-2017-12847 affects Nagios Core versions prior to 4.3.3.
No, CVE-2017-12847 is a local privilege escalation vulnerability that requires local access.
Local users with access to a non-root account can exploit CVE-2017-12847 to kill arbitrary processes.