CVE-2017-16834

PNP4Nagios through 0.6.26 has /usr/bin/npcd and npcd.cfg owned by an unprivileged account but root code execution depends on these files, which allows local users to gain privileges by leveraging access to this unprivileged account.

Published: 2017-11-15 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-16834 is rated Moderate Risk (41.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.36%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-16834

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.36% +0.33%
2 2025-03-30 0.09% 0.03% -0.05%
3 2025-03-29 — 0.09% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-16834

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2017-16834

OS Trackers for CVE-2017-16834

vendor priority summary link
gentoo normal CVE-2017-16834: 1 GLSA(s) (201806-09), 1 atom(s) (net-analyzer/pnp4nagios); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-16834
redhat medium — https://access.redhat.com/security/cve/CVE-2017-16834
ubuntu medium CVE-2017-16834 medium priority: Ubuntu including 1 source packages (pnp4nagios), 7 status rows across 7 suites (artful, bionic, cosmic, trusty, upstream, xenial, zesty): DNE 6, not-affected 1. https://ubuntu.com/security/CVE-2017-16834

Affected software / configurations for CVE-2017-16834

Vendor Product Version Raw CPE
pnp4nagios pnp4nagios <= 0.6.26 cpe:2.3:a:pnp4nagios:pnp4nagios:*:*:*:*:*:*:*:*

References for CVE-2017-16834

cvelogic Threat Intelligence