Learn about CVE-2017-12847 affecting Nagios Core versions prior to 4.3.3. Discover the impact, technical details, and mitigation steps to secure systems against unauthorized process termination.
Nagios Core before version 4.3.3 is susceptible to a vulnerability that could allow local users to terminate processes by exploiting the creation of a nagios.lock PID file. This CVE was published on August 23, 2017, by MITRE.
Understanding CVE-2017-12847
This CVE affects Nagios Core versions prior to 4.3.3 and poses a risk of unauthorized process termination by local users.
What is CVE-2017-12847?
Nagios Core generates a nagios.lock PID file after switching to a non-root account, potentially enabling local users to terminate processes by modifying the file before a root script executes a specific command.
The Impact of CVE-2017-12847
The vulnerability allows local users to kill arbitrary processes by leveraging access to the non-root account for nagios.lock modification before a root script executes a command.
Technical Details of CVE-2017-12847
Nagios Core's vulnerability can be further understood through its technical details.
Vulnerability Description
Before version 4.3.3, Nagios Core creates a nagios.lock PID file after dropping privileges to a non-root account, which could be exploited by local users.
Affected Systems and Versions
Exploitation Mechanism
Local users can exploit access to the non-root account and modify the nagios.lock file before a root script executes a specific command, enabling them to terminate processes.
Mitigation and Prevention
Protecting systems from CVE-2017-12847 requires immediate steps and long-term security practices.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates