CVE-2017-14312
First published: Mon Sep 11 2017(Updated: )
Nagios Core through 4.3.4 initially executes /usr/sbin/nagios as root but supports configuration options in which this file is owned by a non-root account (and similarly can have nagios.cfg owned by a non-root account), which allows local users to gain privileges by leveraging access to this non-root account.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Nagios | <=4.3.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-14312?
CVE-2017-14312 is considered to have a medium severity due to its potential for privilege escalation.
How do I fix CVE-2017-14312?
To fix CVE-2017-14312, ensure that /usr/sbin/nagios and nagios.cfg are owned by the root account and have the appropriate file permissions.
Who is affected by CVE-2017-14312?
CVE-2017-14312 affects users running Nagios Core versions up to and including 4.3.4.
Can CVE-2017-14312 be exploited remotely?
CVE-2017-14312 is a local privilege escalation vulnerability and cannot be exploited remotely.
What versions of Nagios Core are vulnerable to CVE-2017-14312?
Nagios Core versions prior to 4.3.5 are vulnerable to CVE-2017-14312.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/references
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/nagios
- canonical/nagios
- version/nagios/4.3.4