Skip to content
Fencer Vulns
medium 6.3

CVE-2017-12847 json

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 k…

published 2017-08-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-4384

cvss
6.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

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.

Patch / fix

  • nagios openSUSE Tumbleweed 4.4.6-2.5

opensuse advisories openSUSE-SU-2024:11073-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-12847 updated cvss 4.4

nagios: Incorrect permissions for PID file

  • Red Hat Enterprise Linux OpenStack Platform 6 (Juno) nagios Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) nagios, nagios-common
    affected: no fix planned “Will not fix”
  • Red Hat Mobile Application Platform 4 nagios
    affected: no fix planned “Out of support scope”
  • Red Hat Storage 3 nagios, nagios-common
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 6.3 CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.3 AV:L/AC:M/Au:N/C:N/I:C/A:C

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.