CVE-2021-34767 : Détail

CVE-2021-34767

7.4
/
Haute
0.06%V3
Adjacent
2021-09-23
02h26 +00:00
2024-11-07
21h58 +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 XE Software for Catalyst 9800 Series Wireless Controllers IPv6 Denial of Service Vulnerability

A vulnerability in IPv6 traffic processing of Cisco IOS XE Wireless Controller Software for Cisco Catalyst 9000 Family Wireless Controllers could allow an unauthenticated, adjacent attacker to cause a Layer 2 (L2) loop in a configured VLAN, resulting in a denial of service (DoS) condition for that VLAN. The vulnerability is due to a logic error when processing specific link-local IPv6 traffic. An attacker could exploit this vulnerability by sending a crafted IPv6 packet that would flow inbound through the wired interface of an affected device. A successful exploit could allow the attacker to cause traffic drops in the affected VLAN, thus triggering the DoS condition.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-670 Always-Incorrect Control Flow Implementation
The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

Métriques

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

The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).

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 3.3 AV:A/AC:L/Au:N/C:N/I:N/A:P [email protected]

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_xe >> Version *

Cisco>>Ios_xe >> Version 3.15.1xbs

Cisco>>Ios_xe >> Version 3.15.2xbs

Cisco>>Ios_xe >> Version 16.7.1

Cisco>>Ios_xe >> Version 16.7.1a

Cisco>>Ios_xe >> Version 16.7.1b

Cisco>>Ios_xe >> Version 16.7.2

Cisco>>Ios_xe >> Version 16.7.3

Cisco>>Ios_xe >> Version 16.7.4

Cisco>>Ios_xe >> Version 16.8.1

Cisco>>Ios_xe >> Version 16.8.1a

Cisco>>Ios_xe >> Version 16.8.1b

Cisco>>Ios_xe >> Version 16.8.1c

Cisco>>Ios_xe >> Version 16.8.1d

Cisco>>Ios_xe >> Version 16.8.1e

Cisco>>Ios_xe >> Version 16.8.1s

Cisco>>Ios_xe >> Version 16.8.2

Cisco>>Ios_xe >> Version 16.8.3

Cisco>>Ios_xe >> Version 16.9.1

Cisco>>Ios_xe >> Version 16.9.1a

Cisco>>Ios_xe >> Version 16.9.1b

Cisco>>Ios_xe >> Version 16.9.1c

Cisco>>Ios_xe >> Version 16.9.1d

Cisco>>Ios_xe >> Version 16.9.1s

Cisco>>Ios_xe >> Version 16.9.2

Cisco>>Ios_xe >> Version 16.9.2a

Cisco>>Ios_xe >> Version 16.9.2s

Cisco>>Ios_xe >> Version 16.9.3

Cisco>>Ios_xe >> Version 16.9.3a

Cisco>>Ios_xe >> Version 16.9.3h

Cisco>>Ios_xe >> Version 16.9.3s

Cisco>>Ios_xe >> Version 16.9.4

Cisco>>Ios_xe >> Version 16.9.4c

Cisco>>Ios_xe >> Version 16.9.5

Cisco>>Ios_xe >> Version 16.9.5f

Cisco>>Ios_xe >> Version 16.9.6

Cisco>>Ios_xe >> Version 16.9.7

Cisco>>Ios_xe >> Version 16.10.1

Cisco>>Ios_xe >> Version 16.10.1a

Cisco>>Ios_xe >> Version 16.10.1b

Cisco>>Ios_xe >> Version 16.10.1c

Cisco>>Ios_xe >> Version 16.10.1d

Cisco>>Ios_xe >> Version 16.10.1e

Cisco>>Ios_xe >> Version 16.10.1f

Cisco>>Ios_xe >> Version 16.10.1g

Cisco>>Ios_xe >> Version 16.10.1s

Cisco>>Ios_xe >> Version 16.10.2

Cisco>>Ios_xe >> Version 16.10.3

Cisco>>Ios_xe >> Version 16.11.1

Cisco>>Ios_xe >> Version 16.11.1a

Cisco>>Ios_xe >> Version 16.11.1b

Cisco>>Ios_xe >> Version 16.11.1c

Cisco>>Ios_xe >> Version 16.11.1s

Cisco>>Ios_xe >> Version 16.11.2

Cisco>>Ios_xe >> Version 16.12.1

Cisco>>Ios_xe >> Version 16.12.1a

Cisco>>Ios_xe >> Version 16.12.1c

Cisco>>Ios_xe >> Version 16.12.1s

Cisco>>Ios_xe >> Version 16.12.1t

Cisco>>Ios_xe >> Version 16.12.1w

Cisco>>Ios_xe >> Version 16.12.1x

Cisco>>Ios_xe >> Version 16.12.1y

Cisco>>Ios_xe >> Version 16.12.1z

Cisco>>Ios_xe >> Version 16.12.1z1

Cisco>>Ios_xe >> Version 16.12.1za

Cisco>>Ios_xe >> Version 16.12.2

Cisco>>Ios_xe >> Version 16.12.2a

Cisco>>Ios_xe >> Version 16.12.2s

Cisco>>Ios_xe >> Version 16.12.2t

Cisco>>Ios_xe >> Version 16.12.3

Cisco>>Ios_xe >> Version 16.12.3a

Cisco>>Ios_xe >> Version 16.12.3s

Cisco>>Ios_xe >> Version 16.12.4

Cisco>>Ios_xe >> Version 16.12.4a

Cisco>>Ios_xe >> Version 17.1.1

Cisco>>Ios_xe >> Version 17.1.1a

Cisco>>Ios_xe >> Version 17.1.1s

Cisco>>Ios_xe >> Version 17.1.1t

Cisco>>Ios_xe >> Version 17.1.2

Cisco>>Ios_xe >> Version 17.1.3

Cisco>>Ios_xe >> Version 17.2.1

Cisco>>Ios_xe >> Version 17.2.1a

Cisco>>Ios_xe >> Version 17.2.1r

Cisco>>Ios_xe >> Version 17.2.1v

Cisco>>Ios_xe >> Version 17.2.2

Cisco>>Ios_xe >> Version 17.2.3

Cisco>>Ios_xe >> Version 17.3.1

Cisco>>Ios_xe >> Version 17.3.1a

Cisco>>Ios_xe >> Version 17.3.1w

Cisco>>Ios_xe >> Version 17.3.1x

Cisco>>Ios_xe >> Version 17.3.1z

Cisco>>Ios_xe >> Version 17.3.2

Cisco>>Ios_xe >> Version 17.3.2a

Cisco>>Catalyst_9800 >> Version -

Cisco>>Catalyst_9800-40 >> Version -

Cisco>>Catalyst_9800-80 >> Version -

Cisco>>Catalyst_9800-cl >> Version -

Cisco>>Catalyst_9800-l >> Version -

Cisco>>Catalyst_9800-l-c >> Version -

Cisco>>Catalyst_9800-l-f >> Version -

Cisco>>Catalyst_9800_embedded_wireless_controller >> Version -

Références