What is the CVSS score of CVE-2016-9566?

CVE-2016-9566 has a CVSS 3.0 base score of 7.8 (High). CVSS vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 8.6%.

Is there a public PoC exploit available for CVE-2016-9566?

Yes, a public proof-of-concept exploit is available for CVE-2016-9566. Prioritise patching immediately. EPSS: 8.6%.

Is there a patch available for CVE-2016-9566?

Yes, a patch is available for CVE-2016-9566. Update the affected software to the latest version immediately.

Nagios CVE-2016-9566

HIGH

Improper Link Resolution Before File Access (CWE-59)

2016-12-15 cve@mitre.org

Information Disclosure Nagios

7.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Dec 15, 2016 - 22:59 cve.org

HIGH 7.8

DescriptionCVE.org

base/logging.c in Nagios Core before 4.2.4 allows local users with access to an account in the nagios group to gain root privileges via a symlink attack on the log file. NOTE: this can be leveraged by remote attackers using CVE-2016-9565.

AnalysisAI

base/logging.c in Nagios Core before 4.2.4 allows local users with access to an account in the nagios group to gain root privileges via a symlink attack on the log file. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified under CWE-59. base/logging.c in Nagios Core before 4.2.4 allows local users with access to an account in the nagios group to gain root privileges via a symlink attack on the log file. NOTE: this can be leveraged by remote attackers using CVE-2016-9565. Affected products include: Nagios. Version information: before 4.2.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.