CVE-2020-3235 : Detail

CVE-2020-3235

7.7
/
High
A03-Injection
0.3%V4
Network
2020-06-03
17h55 +00:00
2024-11-15
17h11 +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 Simple Network Management Protocol Denial of Service Vulnerability

A vulnerability in the Simple Network Management Protocol (SNMP) subsystem of Cisco IOS Software and Cisco IOS XE Software on Catalyst 4500 Series Switches could allow an authenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to insufficient input validation when the software processes specific SNMP object identifiers. An attacker could exploit this vulnerability by sending a crafted SNMP packet to an affected device. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition. Note: To exploit this vulnerability by using SNMPv2c or earlier, the attacker must know the SNMP read-only community string for an affected system. To exploit this vulnerability by using SNMPv3, the attacker must know the user credentials for the affected system.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-118 Incorrect Access of Indexable Resource ('Range Error')
The product does not restrict or incorrectly restricts operations within the boundaries of a resource that is accessed using an index or pointer, such as memory or files.
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 7.7 HIGH CVSS:3.1/AV:N/AC:L/PR:L/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.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

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 7.7 HIGH CVSS:3.0/AV:N/AC:L/PR:L/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.

Low

The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

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.3 AV:N/AC:M/Au:S/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\(52\)sg

Cisco>>Ios >> Version 12.2\(53\)sg1

Cisco>>Ios >> Version 12.2\(53\)sg2

Cisco>>Ios >> Version 12.2\(53\)sg3

Cisco>>Ios >> Version 12.2\(53\)sg4

Cisco>>Ios >> Version 12.2\(53\)sg5

Cisco>>Ios >> Version 12.2\(53\)sg6

Cisco>>Ios >> Version 12.2\(53\)sg7

Cisco>>Ios >> Version 12.2\(53\)sg8

Cisco>>Ios >> Version 12.2\(53\)sg9

Cisco>>Ios >> Version 12.2\(53\)sg10

Cisco>>Ios >> Version 12.2\(53\)sg11

Cisco>>Ios >> Version 12.2\(54\)sg

Cisco>>Ios >> Version 12.2\(54\)sg1

Cisco>>Ios >> Version 12.2\(54\)wo

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Cisco>>Ios >> Version 15.1\(1\)sg

Cisco>>Ios >> Version 15.1\(1\)sg1

Cisco>>Ios >> Version 15.1\(1\)sg2

Cisco>>Ios >> Version 15.1\(2\)sg

Cisco>>Ios >> Version 15.1\(2\)sg1

Cisco>>Ios >> Version 15.1\(2\)sg2

Cisco>>Ios >> Version 15.1\(2\)sg3

Cisco>>Ios >> Version 15.1\(2\)sg4

Cisco>>Ios >> Version 15.1\(2\)sg5

Cisco>>Ios >> Version 15.1\(2\)sg6

Cisco>>Ios >> Version 15.1\(2\)sg7

Cisco>>Ios >> Version 15.1\(2\)sg8

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

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

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

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\)e9a

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

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

Cisco>>Ios >> Version 15.2\(3\)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\(4\)e

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

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

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

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

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

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

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

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

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

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

Cisco>>Ios_xe >> Version 3.2.0sg

Cisco>>Ios_xe >> Version 3.2.1sg

Cisco>>Ios_xe >> Version 3.2.2sg

Cisco>>Ios_xe >> Version 3.2.3sg

Cisco>>Ios_xe >> Version 3.2.4sg

Cisco>>Ios_xe >> Version 3.2.5sg

Cisco>>Ios_xe >> Version 3.2.6sg

Cisco>>Ios_xe >> Version 3.2.7sg

Cisco>>Ios_xe >> Version 3.2.8sg

Cisco>>Ios_xe >> Version 3.2.9sg

Cisco>>Ios_xe >> Version 3.2.10sg

Cisco>>Ios_xe >> Version 3.2.11sg

Cisco>>Ios_xe >> Version 3.3.0sg

Cisco>>Ios_xe >> Version 3.3.0xo

Cisco>>Ios_xe >> Version 3.3.1sg

Cisco>>Ios_xe >> Version 3.3.1xo

Cisco>>Ios_xe >> Version 3.3.2sg

Cisco>>Ios_xe >> Version 3.3.2xo

Cisco>>Ios_xe >> Version 3.4.0sg

Cisco>>Ios_xe >> Version 3.4.1sg

Cisco>>Ios_xe >> Version 3.4.2sg

Cisco>>Ios_xe >> Version 3.4.3sg

Cisco>>Ios_xe >> Version 3.4.4sg

Cisco>>Ios_xe >> Version 3.4.5sg

Cisco>>Ios_xe >> Version 3.4.6sg

Cisco>>Ios_xe >> Version 3.4.7sg

Cisco>>Ios_xe >> Version 3.4.8sg

Cisco>>Ios_xe >> Version 3.5.0e

Cisco>>Ios_xe >> Version 3.5.1e

Cisco>>Ios_xe >> Version 3.5.2e

Cisco>>Ios_xe >> Version 3.5.3e

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

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>>Catalyst_4503-e >> Version *

Cisco>>Catalyst_4506-e >> Version -

Cisco>>Catalyst_4507r\+e >> Version -

Cisco>>Catalyst_4510r\+e >> Version -

Configuraton 0

Oracle>>Goldengate_management_pack >> Version 12.2.1.2.0

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.