CVE-2022-20625 : Detail

CVE-2022-20625

4.3
/
Medium
0.06%V3
Adjacent
2022-02-23
17h40 +00:00
2024-11-06
16h29 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cisco FXOS and NX-OS Software Cisco Discovery Protocol Service Denial of Service Vulnerability

A vulnerability in the Cisco Discovery Protocol service of Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause the service to restart, resulting in a denial of service (DoS) condition. This vulnerability is due to improper handling of Cisco Discovery Protocol messages that are processed by the Cisco Discovery Protocol service. An attacker could exploit this vulnerability by sending a series of malicious Cisco Discovery Protocol messages to an affected device. A successful exploit could allow the attacker to cause the Cisco Discovery Protocol service to fail and restart. In rare conditions, repeated failures of the process could occur, which could cause the entire device to restart.

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.
CWE Other No informations.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 4.3 MEDIUM CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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.

Unchanged

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

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.

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

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

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>>Firepower_4110 >> Version -

Cisco>>Firepower_4112 >> Version -

Cisco>>Firepower_4115 >> Version -

Cisco>>Firepower_4120 >> Version -

Cisco>>Firepower_4125 >> Version -

Cisco>>Firepower_4140 >> Version -

Cisco>>Firepower_4145 >> Version -

Cisco>>Firepower_4150 >> Version -

Cisco>>Firepower_9300 >> Version -

Cisco>>Firepower_extensible_operating_system >> Version To (excluding) 2.3.1.219

Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.4 To (excluding) 2.9.1.158

Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.10 To (excluding) 2.10.1.179

Configuraton 0

Cisco>>Mds_9132t >> Version -

Cisco>>Mds_9148s >> Version -

Cisco>>Mds_9148t >> Version -

Cisco>>Mds_9222i >> Version -

Cisco>>Mds_9250i >> Version -

Cisco>>Mds_9396s >> Version -

Cisco>>Mds_9396t >> Version -

Cisco>>Mds_9506 >> Version -

Cisco>>Mds_9513 >> Version -

Cisco>>Mds_9706 >> Version -

Cisco>>Mds_9710 >> Version -

Cisco>>Mds_9718 >> Version -

Cisco>>N77-f312ck-26 >> Version -

Cisco>>N77-f324fq-25 >> Version -

Cisco>>N77-f348xp-23 >> Version -

Cisco>>N77-f430cq-36 >> Version -

Cisco>>N77-m312cq-26l >> Version -

Cisco>>N77-m324fq-25l >> Version -

Cisco>>N77-m348xp-23l >> Version -

Cisco>>N7k-f248xp-25e >> Version -

Cisco>>N7k-f306ck-25 >> Version -

Cisco>>N7k-f312fq-25 >> Version -

Cisco>>N7k-m202cf-22l >> Version -

Cisco>>N7k-m206fq-23l >> Version -

Cisco>>N7k-m224xp-23l >> Version -

Cisco>>N7k-m324fq-25l >> Version -

Cisco>>N7k-m348xp-25l >> Version -

Cisco>>Nexus_7000_10-slot >> Version -

Cisco>>Nexus_7000_18-slot >> Version -

Cisco>>Nexus_7000_4-slot >> Version -

Cisco>>Nexus_7000_9-slot >> Version -

Cisco>>Nexus_7000_supervisor_1 >> Version -

Cisco>>Nexus_7000_supervisor_2 >> Version -

Cisco>>Nexus_7000_supervisor_2e >> Version -

Cisco>>Nexus_7700_10-slot >> Version -

Cisco>>Nexus_7700_18-slot >> Version -

Cisco>>Nexus_7700_2-slot >> Version -

Cisco>>Nexus_7700_6-slot >> Version -

Cisco>>Nexus_7700_supervisor_2e >> Version -

Cisco>>Nexus_7700_supervisor_3e >> Version -

Cisco>>Nx-os >> Version 8.2\(7.34\)

Configuraton 0

Cisco>>Nexus_1000v >> Version -

Cisco>>Nexus_1000v >> Version -

Cisco>>Nexus_1000ve >> Version -

Cisco>>Nx-os >> Version 5.2\(1\)sv5\(1.3b\)

Configuraton 0

Cisco>>N9k-c9316d-gx >> Version -

Cisco>>N9k-c9332d-gx2b >> Version -

Cisco>>N9k-c9348d-gx2a >> Version -

Cisco>>N9k-c93600cd-gx >> Version -

Cisco>>N9k-c9364d-gx2a >> Version -

Cisco>>Nexus_1000v >> Version -

Cisco>>Nexus_3048 >> Version -

Cisco>>Nexus_31108pc-v >> Version -

Cisco>>Nexus_31108tc-v >> Version -

Cisco>>Nexus_31128pq >> Version -

Cisco>>Nexus_3132c-z >> Version -

Cisco>>Nexus_3132q-v >> Version -

Cisco>>Nexus_3132q-x >> Version -

Cisco>>Nexus_3132q-xl >> Version -

Cisco>>Nexus_3164q >> Version -

Cisco>>Nexus_3172pq >> Version -

Cisco>>Nexus_3172pq-xl >> Version -

Cisco>>Nexus_3172tq-xl >> Version -

Cisco>>Nexus_3232c >> Version -

Cisco>>Nexus_3264c-e >> Version -

Cisco>>Nexus_3264q >> Version -

Cisco>>Nexus_3408-s >> Version -

Cisco>>Nexus_34180yc >> Version -

Cisco>>Nexus_3432d-s >> Version -

Cisco>>Nexus_3464c >> Version -

Cisco>>Nexus_3524-x >> Version -

Cisco>>Nexus_3524-xl >> Version -

Cisco>>Nexus_3548-x >> Version -

Cisco>>Nexus_3548-xl >> Version -

Cisco>>Nexus_36180yc-r >> Version -

Cisco>>Nexus_3636c-r >> Version -

Cisco>>Nexus_92160yc-x >> Version -

Cisco>>Nexus_92300yc >> Version -

Cisco>>Nexus_92304qc >> Version -

Cisco>>Nexus_92348gc-x >> Version -

Cisco>>Nexus_9236c >> Version -

Cisco>>Nexus_9272q >> Version -

Cisco>>Nexus_93108tc-ex >> Version -

Cisco>>Nexus_93108tc-fx >> Version -

Cisco>>Nexus_93108tc-fx3p >> Version -

Cisco>>Nexus_93120tx >> Version -

Cisco>>Nexus_93216tc-fx2 >> Version -

Cisco>>Nexus_9332c >> Version -

Cisco>>Nexus_9336c-fx2 >> Version -

Cisco>>Nexus_9336c-fx2-e >> Version -

Cisco>>Nexus_9348gc-fxp >> Version -

Cisco>>Nexus_9364c >> Version -

Cisco>>Nexus_9364c-gx >> Version -

Cisco>>Nexus_9504 >> Version -

Cisco>>Nexus_9508 >> Version -

Cisco>>Nexus_9516 >> Version -

Cisco>>Nx-os >> Version 9.3\(8.15\)

Configuraton 0

Cisco>>Ucs_64108 >> Version -

Cisco>>Ucs_6454 >> Version -

Cisco>>Nx-os >> Version 4.0\(1a\)a

Configuraton 0

Cisco>>Ucs_6248up >> Version -

Cisco>>Ucs_6296up >> Version -

Cisco>>Ucs_6324 >> Version -

Cisco>>Ucs_6332 >> Version -

Cisco>>Ucs_6332-16up >> Version -

Cisco>>Nx-os >> Version 4.1\(3f\)c

References