CVE-2020-3569 : Détail

CVE-2020-3569

8.6
/
Haute
0.37%V3
Network
2020-09-23
00h25 +00:00
2024-11-08
16h09 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Cisco IOS XR Software DVMRP Memory Exhaustion Vulnerabilities

Multiple vulnerabilities in the Distance Vector Multicast Routing Protocol (DVMRP) feature of Cisco IOS XR Software could allow an unauthenticated, remote attacker to either immediately crash the Internet Group Management Protocol (IGMP) process or make it consume available memory and eventually crash. The memory consumption may negatively impact other processes that are running on the device. These vulnerabilities are due to the incorrect handling of IGMP packets. An attacker could exploit these vulnerabilities by sending crafted IGMP traffic to an affected device. A successful exploit could allow the attacker to immediately crash the IGMP process or cause memory exhaustion, resulting in other processes becoming unstable. These processes may include, but are not limited to, interior and exterior routing protocols. Cisco will release software updates that address these vulnerabilities.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-400 Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
CWE-770 Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 8.6 HIGH CVSS:3.1/AV:N/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.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more 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 when attacking 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 of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human 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

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

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 a 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 in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.
V2 5 AV:N/AC:L/Au:N/C:N/I:N/A:P [email protected]

CISA KEV (Vulnérabilités Exploitées Connues)

Nom de la vulnérabilité : Cisco IOS XR Software DVMRP Memory Exhaustion Vulnerability

Action requise : Apply updates per vendor instructions.

Connu pour être utilisé dans des campagnes de ransomware : Unknown

Ajouter le : 2021-11-02 23h00 +00:00

Action attendue : 2022-05-02 22h00 +00:00

Informations importantes
Ce CVE est identifié comme vulnérable et constitue une menace active, selon le Catalogue des Vulnérabilités Exploitées Connues (CISA KEV). La CISA a répertorié cette vulnérabilité comme étant activement exploitée par des cybercriminels, soulignant ainsi l'importance de prendre des mesures immédiates pour remédier à cette faille. Il est impératif de prioriser la mise à jour et la correction de ce CVE afin de protéger les systèmes contre les potentielles cyberattaques.

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Cisco>>Ios_xr >> Version 6.1.4

Cisco>>Ios_xr >> Version 6.2.3

Cisco>>Ios_xr >> Version 6.3.3

Cisco>>Ios_xr >> Version 6.4.2

Cisco>>Ios_xr >> Version 6.5.3

Cisco>>Ios_xr >> Version 6.6.2

Cisco>>Ios_xr >> Version 6.6.3

Cisco>>Ios_xr >> Version 7.0.2

Cisco>>Ios_xr >> Version 7.1.2

Cisco>>Ios_xr >> Version 7.1.15

Cisco>>Asr_9000v >> Version -

Cisco>>Asr_9001 >> Version -

Cisco>>Asr_9006 >> Version -

Cisco>>Asr_9010 >> Version -

Cisco>>Asr_9901 >> Version -

Cisco>>Asr_9903 >> Version -

Cisco>>Asr_9904 >> Version -

Cisco>>Asr_9906 >> Version -

Cisco>>Asr_9910 >> Version -

Cisco>>Asr_9912 >> Version -

Cisco>>Asr_9922 >> Version -

Cisco>>Ncs_5001 >> Version -

Cisco>>Ncs_5002 >> Version -

Cisco>>Ncs_5011 >> Version -

Cisco>>Ncs_520 >> Version -

Cisco>>Ncs_540 >> Version -

Cisco>>Ncs_5501 >> Version -

Cisco>>Ncs_5501 >> Version se

Cisco>>Ncs_5502 >> Version -

Cisco>>Ncs_5502 >> Version se

Cisco>>Ncs_5508 >> Version -

Cisco>>Ncs_5516 >> Version -

Cisco>>Ncs_560 >> Version -

Cisco>>Ncs_6008 >> Version -

Configuraton 0

Cisco>>Ios_xr >> Version To (excluding) 6.5.2

Cisco>>Ncs_5001 >> Version -

Cisco>>Ncs_5002 >> Version -

Cisco>>Ncs_5011 >> Version -

Cisco>>Ncs_520 >> Version -

Cisco>>Ncs_540 >> Version -

Cisco>>Ncs_5501 >> Version -

Cisco>>Ncs_5501 >> Version se

Cisco>>Ncs_5502 >> Version -

Cisco>>Ncs_5502 >> Version se

Cisco>>Ncs_5508 >> Version -

Cisco>>Ncs_5516 >> Version -

Cisco>>Ncs_560 >> Version -

Cisco>>Ncs_6008 >> Version -

Configuraton 0

Cisco>>Ios_xr >> Version 6.1.4

Cisco>>Ios_xr >> Version 6.4.2

Cisco>>Ios_xr >> Version 6.4.3

Cisco>>Crs >> Version -

Cisco>>Crs-1_16-slot_line_card_chassis >> Version -

Cisco>>Crs-1_16-slot_single-shelf_system >> Version -

Cisco>>Crs-1_4-slot_single-shelf_system >> Version -

Cisco>>Crs-1_8-slot_line_card_chassis >> Version -

Cisco>>Crs-1_8-slot_single-shelf_system >> Version -

Cisco>>Crs-1_fabric_card_chassis >> Version -

Cisco>>Crs-1_line_card_chassis_\(dual\) >> Version -

Cisco>>Crs-1_line_card_chassis_\(multi\) >> Version -

Cisco>>Crs-1_multishelf_system >> Version -

Cisco>>Crs-3_16-slot_single-shelf_system >> Version -

Cisco>>Crs-3_4-slot_single-shelf_system >> Version -

Cisco>>Crs-3_8-slot_single-shelf_system >> Version -

Cisco>>Crs-3_multishelf_system >> Version -

Cisco>>Crs-8\/s-b_crs >> Version -

Cisco>>Crs-8\/scrs >> Version -

Cisco>>Crs-x >> Version -

Cisco>>Crs-x_16-slot_single-shelf_system >> Version -

Cisco>>Crs-x_multishelf_system >> Version -

Cisco>>Crs_performance_route_processor >> Version -

Références