CVE-2017-12847

Description

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.

Category

6.3
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.11%
Vendor Advisory gentoo.org Vendor Advisory github.com Vendor Advisory github.com Vendor Advisory github.com Vendor Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2017-12847?
CVE-2017-12847 has been scored as a medium severity vulnerability.
How to fix CVE-2017-12847?
To fix CVE-2017-12847, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-12847 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-12847 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.