Check Diskio up to 3.2.5 source code

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Check Diskio up to 3.2.5. This affects an unknown function. The manipulation results in source code. This vulnerability is identified as CVE-2014-8994. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Check Diskio up to 3.2.5. Affected is some unknown functionality. The manipulation with an unknown input leads to a source code vulnerability. CWE is classifying the issue as CWE-18. This is going to have an impact on integrity, and availability. CVE summarizes:

The check_diskio plugin 3.2.6 and earlier for Nagios and Icinga allows local users to write to arbitrary files via a symlink attack on a temporary file with a predictable name (tmp/check_diskio_status-*-*).

The weakness was released 11/28/2014 (Website). The advisory is available at xforce.iss.net. This vulnerability is traded as CVE-2014-8994 since 11/19/2014. The exploitability is told to be easy. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (98849) and SecurityFocus (BID 71208†). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.1
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Source code
CWE: CWE-18 / CWE-17
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/19/2014 🔍
11/20/2014 +1 days 🔍
11/28/2014 +8 days 🔍
11/28/2014 +0 days 🔍
03/27/2015 +119 days 🔍
04/06/2018 +1106 days 🔍

Sourcesinfo

Advisory: xforce.iss.net
Status: Not defined

CVE: CVE-2014-8994 (🔍)
GCVE (CVE): GCVE-0-2014-8994
GCVE (VulDB): GCVE-100-73026
X-Force: 98849
SecurityFocus: 71208 - check_diskio CVE-2014-8994 Symlink Vulnerability

Entryinfo

Created: 03/27/2015 14:56
Updated: 04/06/2018 11:49
Changes: 03/27/2015 14:56 (43), 04/06/2018 11:49 (6)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!