CVE Intelligence
Skip to main content
MEDIUMpublic exploit

CVE-2016-8641

CVE-2016-8641 Vulnerability Analysis & Exploit Intelligence

A privilege escalation vulnerability was found in nagios 4.2.x that occurs in daemon-init.in when creating necessary files and insecurely changing the ownership afterwards. It's possible for the local attacker to create symbolic links before the files are to be created and possibly escalating the privileges with the ownership change.

Published Updated Sources: cvelistV5, redhat

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

1%

chance of exploitation in 30 days

Affects

nagios enterprises

nagios

CVSS base

6.7

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Products (1)

nagios

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.7CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-59

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1547.009Boot or Logon Autostart Execution: Shortcut Modification
  • T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
  • T1574.010Hijack Execution Flow: Services File Permissions Weakness

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

exploit db

References

5 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.