CVE-2020-3225 : Detail

CVE-2020-3225

8.6
/
High
A03-Injection
1.95%V4
Network
2020-06-03
17h42 +00:00
2024-11-15
17h14 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cisco IOS and IOS XE Software Common Industrial Protocol Denial of Service Vulnerabilities

Multiple vulnerabilities in the implementation of the Common Industrial Protocol (CIP) feature of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to reload, resulting in a denial of service (DoS) condition. The vulnerabilities are due to insufficient input processing of CIP traffic. An attacker could exploit these vulnerabilities by sending crafted CIP traffic to be processed by an affected device. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a 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.

Metrics

Metrics Score Severity CVSS Vector 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.

 nvd@nist.gov
V3.0 8.6 HIGH CVSS:3.0/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

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.

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 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>>Ios >> Version 12.2\(44\)ex

Cisco>>Ios >> Version 12.2\(44\)ex1

Cisco>>Ios >> Version 12.2\(46\)se1

Cisco>>Ios >> Version 12.2\(46\)se2

Cisco>>Ios >> Version 12.2\(50\)se

Cisco>>Ios >> Version 12.2\(50\)se1

Cisco>>Ios >> Version 12.2\(50\)se2

Cisco>>Ios >> Version 12.2\(50\)se3

Cisco>>Ios >> Version 12.2\(50\)se4

Cisco>>Ios >> Version 12.2\(50\)se5

Cisco>>Ios >> Version 12.2\(52\)se

Cisco>>Ios >> Version 12.2\(52\)se1

Cisco>>Ios >> Version 12.2\(55\)se

Cisco>>Ios >> Version 12.2\(55\)se3

Cisco>>Ios >> Version 12.2\(55\)se4

Cisco>>Ios >> Version 12.2\(55\)se5

Cisco>>Ios >> Version 12.2\(55\)se6

Cisco>>Ios >> Version 12.2\(55\)se7

Cisco>>Ios >> Version 12.2\(55\)se9

Cisco>>Ios >> Version 12.2\(55\)se10

Cisco>>Ios >> Version 12.2\(55\)se11

Cisco>>Ios >> Version 12.2\(55\)se12

Cisco>>Ios >> Version 12.2\(55\)se13

Cisco>>Ios >> Version 12.2\(55\)se13a

Cisco>>Ios >> Version 12.2\(58\)se

Cisco>>Ios >> Version 12.2\(58\)se1

Cisco>>Ios >> Version 12.2\(58\)se2

Cisco>>Ios >> Version 12.2\(60\)ez16

Cisco>>Ios >> Version 15.0\(1\)ey

Cisco>>Ios >> Version 15.0\(1\)ey1

Cisco>>Ios >> Version 15.0\(1\)ey2

Cisco>>Ios >> Version 15.0\(2\)ek

Cisco>>Ios >> Version 15.0\(2\)ek1

Cisco>>Ios >> Version 15.0\(2\)ex2

Cisco>>Ios >> Version 15.0\(2\)ex8

Cisco>>Ios >> Version 15.0\(2\)ey

Cisco>>Ios >> Version 15.0\(2\)ey1

Cisco>>Ios >> Version 15.0\(2\)ey2

Cisco>>Ios >> Version 15.0\(2\)ey3

Cisco>>Ios >> Version 15.0\(2\)se

Cisco>>Ios >> Version 15.0\(2\)se1

Cisco>>Ios >> Version 15.0\(2\)se2

Cisco>>Ios >> Version 15.0\(2\)se3

Cisco>>Ios >> Version 15.0\(2\)se4

Cisco>>Ios >> Version 15.0\(2\)se5

Cisco>>Ios >> Version 15.0\(2\)se6

Cisco>>Ios >> Version 15.0\(2\)se7

Cisco>>Ios >> Version 15.0\(2\)se8

Cisco>>Ios >> Version 15.0\(2\)se9

Cisco>>Ios >> Version 15.0\(2\)se10

Cisco>>Ios >> Version 15.0\(2\)se10a

Cisco>>Ios >> Version 15.0\(2\)se11

Cisco>>Ios >> Version 15.0\(2\)se12

Cisco>>Ios >> Version 15.0\(2\)se13

Cisco>>Ios >> Version 15.0\(2\)se13a

Cisco>>Ios >> Version 15.0\(2\)sg11a

Cisco>>Ios >> Version 15.2\(1\)ey

Cisco>>Ios >> Version 15.2\(2\)e

Cisco>>Ios >> Version 15.2\(2\)e1

Cisco>>Ios >> Version 15.2\(2\)e2

Cisco>>Ios >> Version 15.2\(2\)e3

Cisco>>Ios >> Version 15.2\(2\)e4

Cisco>>Ios >> Version 15.2\(2\)e5

Cisco>>Ios >> Version 15.2\(2\)e5a

Cisco>>Ios >> Version 15.2\(2\)e5b

Cisco>>Ios >> Version 15.2\(2\)e6

Cisco>>Ios >> Version 15.2\(2\)e7

Cisco>>Ios >> Version 15.2\(2\)e7b

Cisco>>Ios >> Version 15.2\(2\)e8

Cisco>>Ios >> Version 15.2\(2\)e9

Cisco>>Ios >> Version 15.2\(2\)e10

Cisco>>Ios >> Version 15.2\(2\)ea

Cisco>>Ios >> Version 15.2\(2\)ea1

Cisco>>Ios >> Version 15.2\(2\)ea2

Cisco>>Ios >> Version 15.2\(2\)ea3

Cisco>>Ios >> Version 15.2\(2\)eb

Cisco>>Ios >> Version 15.2\(2\)eb1

Cisco>>Ios >> Version 15.2\(2\)eb2

Cisco>>Ios >> Version 15.2\(2b\)e

Cisco>>Ios >> Version 15.2\(3\)e1

Cisco>>Ios >> Version 15.2\(3\)e2

Cisco>>Ios >> Version 15.2\(3\)e3

Cisco>>Ios >> Version 15.2\(3\)e4

Cisco>>Ios >> Version 15.2\(3\)e5

Cisco>>Ios >> Version 15.2\(3\)ea

Cisco>>Ios >> Version 15.2\(4\)e9

Cisco>>Ios >> Version 15.2\(4\)e10

Cisco>>Ios >> Version 15.2\(4\)ea

Cisco>>Ios >> Version 15.2\(4\)ea1

Cisco>>Ios >> Version 15.2\(4\)ea2

Cisco>>Ios >> Version 15.2\(4\)ea3

Cisco>>Ios >> Version 15.2\(4\)ea4

Cisco>>Ios >> Version 15.2\(4\)ea5

Cisco>>Ios >> Version 15.2\(4\)ea6

Cisco>>Ios >> Version 15.2\(4\)ea7

Cisco>>Ios >> Version 15.2\(4\)ea8

Cisco>>Ios >> Version 15.2\(4\)ea9

Cisco>>Ios >> Version 15.2\(4\)ec1

Cisco>>Ios >> Version 15.2\(4\)ec2

Cisco>>Ios >> Version 15.2\(4\)jaz

Cisco>>Ios >> Version 15.2\(4\)jaz1

Cisco>>Ios >> Version 15.2\(5\)e

Cisco>>Ios >> Version 15.2\(5\)e1

Cisco>>Ios >> Version 15.2\(5\)e2

Cisco>>Ios >> Version 15.2\(5\)e2b

Cisco>>Ios >> Version 15.2\(5\)e2c

Cisco>>Ios >> Version 15.2\(5\)ea

Cisco>>Ios >> Version 15.2\(5a\)e1

Cisco>>Ios >> Version 15.2\(6\)e

Cisco>>Ios >> Version 15.2\(6\)e0a

Cisco>>Ios >> Version 15.2\(6\)e0c

Cisco>>Ios >> Version 15.2\(6\)e1

Cisco>>Ios >> Version 15.2\(6\)e1a

Cisco>>Ios >> Version 15.2\(6\)e1s

Cisco>>Ios >> Version 15.2\(6\)e2a

Cisco>>Ios >> Version 15.2\(6\)e3

Cisco>>Ios >> Version 15.2\(6\)eb

Cisco>>Ios >> Version 15.2\(7\)e

Cisco>>Ios >> Version 15.2\(7\)e0b

Cisco>>Ios >> Version 15.2\(7\)e0s

Cisco>>Ios >> Version 15.2\(7a\)e0b

Cisco>>Ios >> Version 15.2\(7b\)e0b

Cisco>>Ios >> Version 15.3\(3\)ja1

Cisco>>Ios >> Version 15.3\(3\)ja1n

Cisco>>Ios >> Version 15.3\(3\)ja4

Cisco>>Ios >> Version 15.3\(3\)ja5

Cisco>>Ios >> Version 15.3\(3\)ja6

Cisco>>Ios >> Version 15.3\(3\)ja7

Cisco>>Ios >> Version 15.3\(3\)ja8

Cisco>>Ios >> Version 15.3\(3\)ja10

Cisco>>Ios >> Version 15.3\(3\)ja11

Cisco>>Ios >> Version 15.3\(3\)ja12

Cisco>>Ios >> Version 15.3\(3\)jaa

Cisco>>Ios >> Version 15.3\(3\)jaa1

Cisco>>Ios >> Version 15.3\(3\)jax

Cisco>>Ios >> Version 15.3\(3\)jax1

Cisco>>Ios >> Version 15.3\(3\)jax2

Cisco>>Ios >> Version 15.3\(3\)jb

Cisco>>Ios >> Version 15.3\(3\)jbb

Cisco>>Ios >> Version 15.3\(3\)jbb1

Cisco>>Ios >> Version 15.3\(3\)jbb2

Cisco>>Ios >> Version 15.3\(3\)jbb4

Cisco>>Ios >> Version 15.3\(3\)jbb5

Cisco>>Ios >> Version 15.3\(3\)jbb6

Cisco>>Ios >> Version 15.3\(3\)jbb6a

Cisco>>Ios >> Version 15.3\(3\)jbb8

Cisco>>Ios >> Version 15.3\(3\)jc

Cisco>>Ios >> Version 15.3\(3\)jc1

Cisco>>Ios >> Version 15.3\(3\)jc2

Cisco>>Ios >> Version 15.3\(3\)jc3

Cisco>>Ios >> Version 15.3\(3\)jc4

Cisco>>Ios >> Version 15.3\(3\)jc5

Cisco>>Ios >> Version 15.3\(3\)jc6

Cisco>>Ios >> Version 15.3\(3\)jc8

Cisco>>Ios >> Version 15.3\(3\)jc9

Cisco>>Ios >> Version 15.3\(3\)jc14

Cisco>>Ios >> Version 15.3\(3\)jd

Cisco>>Ios >> Version 15.3\(3\)jd2

Cisco>>Ios >> Version 15.3\(3\)jd3

Cisco>>Ios >> Version 15.3\(3\)jd4

Cisco>>Ios >> Version 15.3\(3\)jd5

Cisco>>Ios >> Version 15.3\(3\)jd6

Cisco>>Ios >> Version 15.3\(3\)jd7

Cisco>>Ios >> Version 15.3\(3\)jd8

Cisco>>Ios >> Version 15.3\(3\)jd9

Cisco>>Ios >> Version 15.3\(3\)jd11

Cisco>>Ios >> Version 15.3\(3\)jd12

Cisco>>Ios >> Version 15.3\(3\)jd13

Cisco>>Ios >> Version 15.3\(3\)jd14

Cisco>>Ios >> Version 15.3\(3\)jd16

Cisco>>Ios >> Version 15.3\(3\)jd17

Cisco>>Ios >> Version 15.3\(3\)je

Cisco>>Ios >> Version 15.3\(3\)jf

Cisco>>Ios >> Version 15.3\(3\)jf1

Cisco>>Ios >> Version 15.3\(3\)jf2

Cisco>>Ios >> Version 15.3\(3\)jf4

Cisco>>Ios >> Version 15.3\(3\)jf5

Cisco>>Ios >> Version 15.3\(3\)jf6

Cisco>>Ios >> Version 15.3\(3\)jf7

Cisco>>Ios >> Version 15.3\(3\)jf8

Cisco>>Ios >> Version 15.3\(3\)jf9

Cisco>>Ios >> Version 15.3\(3\)jf10

Cisco>>Ios >> Version 15.3\(3\)jf13

Cisco>>Ios >> Version 15.3\(3\)jf99

Cisco>>Ios >> Version 15.3\(3\)jg

Cisco>>Ios >> Version 15.3\(3\)jg1

Cisco>>Ios >> Version 15.3\(3\)jh

Cisco>>Ios >> Version 15.3\(3\)jh1

Cisco>>Ios >> Version 15.3\(3\)ji1

Cisco>>Ios >> Version 15.3\(3\)ji3

Cisco>>Ios >> Version 15.3\(3\)ji4

Cisco>>Ios >> Version 15.3\(3\)ji5

Cisco>>Ios >> Version 15.3\(3\)jj

Cisco>>Ios >> Version 15.3\(3\)jj1

Cisco>>Ios >> Version 15.3\(3\)jk

Cisco>>Ios >> Version 15.3\(3\)jk1a

Cisco>>Ios >> Version 15.3\(3\)jk1t

Cisco>>Ios >> Version 15.3\(3\)jk2a

Cisco>>Ios >> Version 15.3\(3\)jk3

Cisco>>Ios >> Version 15.3\(3\)jk99

Cisco>>Ios >> Version 15.3\(3\)jn

Cisco>>Ios >> Version 15.3\(3\)jn1

Cisco>>Ios >> Version 15.3\(3\)jn2

Cisco>>Ios >> Version 15.3\(3\)jn3

Cisco>>Ios >> Version 15.3\(3\)jn4

Cisco>>Ios >> Version 15.3\(3\)jn6

Cisco>>Ios >> Version 15.3\(3\)jn7

Cisco>>Ios >> Version 15.3\(3\)jn8

Cisco>>Ios >> Version 15.3\(3\)jn9

Cisco>>Ios >> Version 15.3\(3\)jn11

Cisco>>Ios >> Version 15.3\(3\)jn13

Cisco>>Ios >> Version 15.3\(3\)jn14

Cisco>>Ios >> Version 15.3\(3\)jn15

Cisco>>Ios >> Version 15.3\(3\)jnb

Cisco>>Ios >> Version 15.3\(3\)jnb1

Cisco>>Ios >> Version 15.3\(3\)jnb2

Cisco>>Ios >> Version 15.3\(3\)jnb3

Cisco>>Ios >> Version 15.3\(3\)jnb4

Cisco>>Ios >> Version 15.3\(3\)jnb5

Cisco>>Ios >> Version 15.3\(3\)jnb6

Cisco>>Ios >> Version 15.3\(3\)jnc

Cisco>>Ios >> Version 15.3\(3\)jnc1

Cisco>>Ios >> Version 15.3\(3\)jnc2

Cisco>>Ios >> Version 15.3\(3\)jnc3

Cisco>>Ios >> Version 15.3\(3\)jnc4

Cisco>>Ios >> Version 15.3\(3\)jnd

Cisco>>Ios >> Version 15.3\(3\)jnd1

Cisco>>Ios >> Version 15.3\(3\)jnd2

Cisco>>Ios >> Version 15.3\(3\)jnd3

Cisco>>Ios >> Version 15.3\(3\)jnp

Cisco>>Ios >> Version 15.3\(3\)jnp1

Cisco>>Ios >> Version 15.3\(3\)jnp3

Cisco>>Ios >> Version 15.3\(3\)jpb

Cisco>>Ios >> Version 15.3\(3\)jpb1

Cisco>>Ios >> Version 15.3\(3\)jpc

Cisco>>Ios >> Version 15.3\(3\)jpc1

Cisco>>Ios >> Version 15.3\(3\)jpc2

Cisco>>Ios >> Version 15.3\(3\)jpc3

Cisco>>Ios >> Version 15.3\(3\)jpc5

Cisco>>Ios >> Version 15.3\(3\)jpc99

Cisco>>Ios >> Version 15.3\(3\)jpd

Cisco>>Ios >> Version 15.3\(3\)jpi

Cisco>>Ios >> Version 15.3\(3\)jpi3

Cisco>>Ios >> Version 15.3\(3\)jpj

Cisco>>Ios_xe >> Version 3.3.0xo

Cisco>>Ios_xe >> Version 3.3.1xo

Cisco>>Ios_xe >> Version 3.3.2xo

Cisco>>Ios_xe >> Version 3.6.5be

Cisco>>Ios_xe >> Version 3.8.9e

Cisco>>Ios_xe >> Version 3.8.10e

Cisco>>Ios_xe >> Version 3.10.3e

Cisco>>Ios_xe >> Version 16.3.9

Cisco>>Ios_xe >> Version 16.3.10

Cisco>>Ios_xe >> Version 16.6.7

Cisco>>Ios_xe >> Version 16.6.7a

Cisco>>Ios_xe >> Version 16.6.8

Cisco>>Ios_xe >> Version 16.9.1

Cisco>>Ios_xe >> Version 16.9.1d

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.10.1

Cisco>>Ios_xe >> Version 16.10.1e

Cisco>>Ios_xe >> Version 16.10.1g

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.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

References

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.