CVE-2019-1750 : Detail

CVE-2019-1750

7.4
/
High
A03-Injection
0.15%V4
Adjacent
2019-03-27
23h55 +00:00
2024-11-21
19h41 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cisco IOS XE Software Catalyst 4500 Cisco Discovery Protocol Denial of Service Vulnerability

A vulnerability in the Easy Virtual Switching System (VSS) of Cisco IOS XE Software on Catalyst 4500 Series Switches could allow an unauthenticated, adjacent attacker to cause the switches to reload. The vulnerability is due to incomplete error handling when processing Cisco Discovery Protocol (CDP) packets used with the Easy Virtual Switching System. An attacker could exploit this vulnerability by sending a specially crafted CDP packet. An exploit could allow the attacker to cause the device to reload, resulting in a denial of service (DoS) condition.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-20 Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-388 Category : 7PK - Errors
This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, "Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle."

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 7.4 HIGH CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/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.

Adjacent

A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router).

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.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

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
V2 6.1 AV:A/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>>Ios_xe >> Version 3.6.0ae

Cisco>>Ios_xe >> Version 3.6.0be

Cisco>>Ios_xe >> Version 3.6.0e

Cisco>>Ios_xe >> Version 3.6.1e

Cisco>>Ios_xe >> Version 3.6.2ae

Cisco>>Ios_xe >> Version 3.6.2e

Cisco>>Ios_xe >> Version 3.6.3e

Cisco>>Ios_xe >> Version 3.6.4e

Cisco>>Ios_xe >> Version 3.6.5ae

Cisco>>Ios_xe >> Version 3.6.5be

Cisco>>Ios_xe >> Version 3.6.5e

Cisco>>Ios_xe >> Version 3.6.6e

Cisco>>Ios_xe >> Version 3.6.7ae

Cisco>>Ios_xe >> Version 3.6.7be

Cisco>>Ios_xe >> Version 3.6.7e

Cisco>>Ios_xe >> Version 3.6.8e

Cisco>>Ios_xe >> Version 3.6.9e

Cisco>>Ios_xe >> Version 3.6.10e

Cisco>>Ios_xe >> Version 3.7.0e

Cisco>>Ios_xe >> Version 3.7.1e

Cisco>>Ios_xe >> Version 3.7.2e

Cisco>>Ios_xe >> Version 3.7.3e

Cisco>>Ios_xe >> Version 3.8.0e

Cisco>>Ios_xe >> Version 3.8.1e

Cisco>>Ios_xe >> Version 3.8.2e

Cisco>>Ios_xe >> Version 3.8.3e

Cisco>>Ios_xe >> Version 3.8.4e

Cisco>>Ios_xe >> Version 3.8.5ae

Cisco>>Ios_xe >> Version 3.8.5e

Cisco>>Ios_xe >> Version 3.8.6e

Cisco>>Ios_xe >> Version 3.8.7e

Cisco>>Ios_xe >> Version 3.9.0e

Cisco>>Ios_xe >> Version 3.9.1e

Cisco>>Ios_xe >> Version 3.9.2be

Cisco>>Ios_xe >> Version 3.9.2e

Cisco>>Ios_xe >> Version 3.10.0ce

Cisco>>Ios_xe >> Version 3.10.0e

Cisco>>Ios_xe >> Version 3.10.1ae

Cisco>>Ios_xe >> Version 3.10.1e

Cisco>>Ios_xe >> Version 3.10.1se

Cisco>>Ios_xe >> Version 3.10.2e

Cisco>>Ios_xe >> Version 16.9.2h

References

http://www.securityfocus.com/bid/107607
Tags : vdb-entry, x_refsource_BID
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.