CVE-2017-16882
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIcinga Core through 1.14.0 initially executes bin/icinga as root but supports configuration options in which this file is owned by a non-root account (and similarly can have etc/icinga.cfg owned by a non-root account), which allows local users to gain privileges by leveraging access to this non-root account, a related issue to CVE-2017-14312. This also affects bin/icingastats, bin/ido2db, and bin/log2ido.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIcinga Core through 1.14.0 runs binaries (bin/icinga, bin/icingastats, bin/ido2db, bin/log2db) as root but allows configuration options to set file ownership to non-root accounts. Local attackers with access to these non-root accounts can modify the root-owned binaries or etc/icinga.cfg to execute arbitrary code with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.14.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Icinga Core versionRun 'icinga --version' or check package manager for installed icinga versionAffected if Version is 1.14.0 or lower (any version through 1.14.0)
-
Verify ownership of icinga binaryRun 'ls -la' on bin/icinga or /usr/sbin/icinga to check the ownerAffected if File is owned by a non-root user (any user other than root)
-
Verify ownership of icingastats binaryRun 'ls -la' on bin/icingastats to check the ownerAffected if File is owned by a non-root user
-
Verify ownership of ido2db binaryRun 'ls -la' on bin/ido2db to check the ownerAffected if File is owned by a non-root user
-
Verify ownership of log2db binaryRun 'ls -la' on bin/log2db to check the ownerAffected if File is owned by a non-root user
-
Verify ownership of icinga.cfgLocate and check ownership of the main icinga.cfg configuration fileAffected if Configuration file is owned by a non-root user
You are affected if Icinga Core version is 1.14.0 or lower AND any of the binaries (icinga, icingastats, ido2db, log2db) or the icinga.cfg configuration file is owned by a non-root account.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnsure all Icinga binaries and configuration files (especially bin/icinga, bin/icingastats, bin/ido2db, bin/log2ido, and etc/icinga.cfg) are owned by root with appropriate permissions, preventing modification by non-root users.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-16882 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data