CVE-2015-0718 : Detail

CVE-2015-0718

7.5
/
High
0.57%V3
Network
2016-03-03
21h00 +00:00
2016-12-01
14h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cisco NX-OS 4.0 through 6.1 on Nexus 1000V 3000, 4000, 5000, 6000, and 7000 devices and Unified Computing System (UCS) platforms allows remote attackers to cause a denial of service (TCP stack reload) by sending crafted TCP packets to a device that has a TIME_WAIT TCP session, aka Bug ID CSCub70579.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-399 Category : Resource Management Errors
Weaknesses in this category are related to improper management of system resources.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 7.5 HIGH CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

 nvd@nist.gov
V2 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Cisco>>Unified_computing_system >> Version 1.4_1i

Cisco>>Unified_computing_system >> Version 1.4_1j

Cisco>>Unified_computing_system >> Version 1.4_1m

Cisco>>Unified_computing_system >> Version 1.4_3i

Cisco>>Unified_computing_system >> Version 1.4_3l

Cisco>>Unified_computing_system >> Version 1.4_3m

Cisco>>Unified_computing_system >> Version 1.4_3q

Cisco>>Unified_computing_system >> Version 1.4_3s

Cisco>>Unified_computing_system >> Version 1.4_3u

Cisco>>Unified_computing_system >> Version 1.4_3y

Cisco>>Unified_computing_system >> Version 1.4_4f

Cisco>>Unified_computing_system >> Version 1.4_4g

Cisco>>Unified_computing_system >> Version 1.4_4i

Cisco>>Unified_computing_system >> Version 1.4_4j

Cisco>>Unified_computing_system >> Version 1.4_4k

Cisco>>Unified_computing_system >> Version 1.4_4l

Cisco>>Unified_computing_system >> Version 1.5_base

Cisco>>Unified_computing_system >> Version 1.6_base

Cisco>>Unified_computing_system >> Version 2.0_1q

Cisco>>Unified_computing_system >> Version 2.0_1s

Cisco>>Unified_computing_system >> Version 2.0_1t

Cisco>>Unified_computing_system >> Version 2.0_1w

Cisco>>Unified_computing_system >> Version 2.0_1x

Cisco>>Unified_computing_system >> Version 2.0_2m

Cisco>>Unified_computing_system >> Version 2.0_2q

Cisco>>Unified_computing_system >> Version 2.0_2r

Cisco>>Unified_computing_system >> Version 2.0_3a

Cisco>>Unified_computing_system >> Version 2.0_3b

Cisco>>Unified_computing_system >> Version 2.0_3c

Cisco>>Unified_computing_system >> Version 2.0_4a

Cisco>>Unified_computing_system >> Version 2.0_4b

Cisco>>Unified_computing_system >> Version 2.0_4d

Cisco>>Unified_computing_system >> Version 2.0_5a

Cisco>>Unified_computing_system >> Version 2.0_5b

Cisco>>Unified_computing_system >> Version 2.0_5c

Cisco>>Unified_computing_system >> Version 2.0_5d

Cisco>>Unified_computing_system >> Version 2.0_5e

Cisco>>Unified_computing_system >> Version 2.0_5f

Cisco>>Unified_computing_system >> Version 2.1_1a

Cisco>>Unified_computing_system >> Version 2.1_1b

Cisco>>Unified_computing_system >> Version 2.1_1d

Cisco>>Unified_computing_system >> Version 2.1_1e

Cisco>>Unified_computing_system >> Version 2.1_1f

Cisco>>Unified_computing_system >> Version 2.1_2a

Cisco>>Unified_computing_system >> Version 2.1_2c

Cisco>>Unified_computing_system >> Version 2.1_2d

Cisco>>Unified_computing_system >> Version 2.1_3a

Cisco>>Unified_computing_system >> Version 2.1_3b

Cisco>>Unified_computing_system >> Version 2.1_3c

Cisco>>Unified_computing_system >> Version 2.1_3d

Cisco>>Unified_computing_system >> Version 2.1_3e

Cisco>>Unified_computing_system >> Version 2.1_3f

Cisco>>Unified_computing_system >> Version 2.2_1b

Cisco>>Unified_computing_system >> Version 2.2_1c

Cisco>>Unified_computing_system >> Version 2.2_1d

Cisco>>Unified_computing_system >> Version 2.2_1e

Cisco>>Unified_computing_system >> Version 2.2_2c

Cisco>>Unified_computing_system >> Version 2.2_2d

Cisco>>Unified_computing_system >> Version 2.2_2e

Cisco>>Nx-os >> Version base

Netgear>>Jr6150_firmware >> Version To (excluding) 2017-01-06

Samsung>>X14j_firmware >> Version t-ms14jakucb-1102.5

Sun>>Opensolaris >> Version snv_124

    Zyxel>>Gs1900-10hp_firmware >> Version To (excluding) 2.50\(aazi.0\)c0

    Zzinc>>Keymouse_firmware >> Version 3.08

    References

    http://www.securitytracker.com/id/1035159
    Tags : vdb-entry, x_refsource_SECTRACK
    http://www.securitytracker.com/id/1035160
    Tags : vdb-entry, x_refsource_SECTRACK