CVE-2019-1738 : Détail

CVE-2019-1738

7.5
/
Haute
A03-Injection
0.09%V3
Network
2019-03-27
23h15 +00:00
2024-11-19
19h14 +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 and IOS XE Software Network-Based Application Recognition Denial of Service Vulnerability

A vulnerability in the Network-Based Application Recognition (NBAR) feature of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to reload. This vulnerability is due to a parsing issue on DNS packets. An attacker could exploit these vulnerabilities by sending crafted DNS packets through routers that are running an affected version and have NBAR enabled. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a denial of service (DoS) condition.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse 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.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.

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.

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.

 [email protected]
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 [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 >> Version 15.1\(2\)sg8a

Cisco>>Ios >> Version 15.1\(3\)svg3d

Cisco>>Ios >> Version 15.1\(3\)svi1b

Cisco>>Ios >> Version 15.1\(3\)svk4b

Cisco>>Ios >> Version 15.1\(3\)svk4c

Cisco>>Ios >> Version 15.1\(3\)svm3

Cisco>>Ios >> Version 15.1\(3\)svn2

Cisco>>Ios >> Version 15.1\(3\)svo1

Cisco>>Ios >> Version 15.1\(3\)svo2

Cisco>>Ios >> Version 15.1\(3\)svo3

Cisco>>Ios >> Version 15.1\(3\)svo4

Cisco>>Ios >> Version 15.1\(3\)svp1

Cisco>>Ios >> Version 15.1\(3\)svp2

Cisco>>Ios >> Version 15.1\(4\)m12c

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

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

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

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

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

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

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

Cisco>>Ios >> Version 15.5\(3\)m

Cisco>>Ios >> Version 15.5\(3\)m0a

Cisco>>Ios >> Version 15.5\(3\)m1

Cisco>>Ios >> Version 15.5\(3\)m2

Cisco>>Ios >> Version 15.5\(3\)m2a

Cisco>>Ios >> Version 15.5\(3\)m3

Cisco>>Ios >> Version 15.5\(3\)m4

Cisco>>Ios >> Version 15.5\(3\)m4a

Cisco>>Ios >> Version 15.5\(3\)m4b

Cisco>>Ios >> Version 15.5\(3\)m4c

Cisco>>Ios >> Version 15.5\(3\)m5

Cisco>>Ios >> Version 15.5\(3\)m5a

Cisco>>Ios >> Version 15.5\(3\)s

Cisco>>Ios >> Version 15.5\(3\)s0a

Cisco>>Ios >> Version 15.5\(3\)s1

Cisco>>Ios >> Version 15.5\(3\)s1a

Cisco>>Ios >> Version 15.5\(3\)s2

Cisco>>Ios >> Version 15.5\(3\)s3

Cisco>>Ios >> Version 15.5\(3\)s4

Cisco>>Ios >> Version 15.5\(3\)s5

Cisco>>Ios >> Version 15.5\(3\)sn

Cisco>>Ios >> Version 15.5\(3\)sn0a

Cisco>>Ios >> Version 15.6\(1\)s

Cisco>>Ios >> Version 15.6\(1\)s1

Cisco>>Ios >> Version 15.6\(1\)s2

Cisco>>Ios >> Version 15.6\(1\)s3

Cisco>>Ios >> Version 15.6\(1\)s4

Cisco>>Ios >> Version 15.6\(1\)sn

Cisco>>Ios >> Version 15.6\(1\)sn1

Cisco>>Ios >> Version 15.6\(1\)sn2

Cisco>>Ios >> Version 15.6\(1\)sn3

Cisco>>Ios >> Version 15.6\(1\)t

Cisco>>Ios >> Version 15.6\(1\)t0a

Cisco>>Ios >> Version 15.6\(1\)t1

Cisco>>Ios >> Version 15.6\(1\)t2

Cisco>>Ios >> Version 15.6\(2\)s

Cisco>>Ios >> Version 15.6\(2\)s1

Cisco>>Ios >> Version 15.6\(2\)s2

Cisco>>Ios >> Version 15.6\(2\)s3

Cisco>>Ios >> Version 15.6\(2\)s4

Cisco>>Ios >> Version 15.6\(2\)sn

Cisco>>Ios >> Version 15.6\(2\)sp3b

Cisco>>Ios >> Version 15.6\(2\)t

Cisco>>Ios >> Version 15.6\(2\)t0a

Cisco>>Ios >> Version 15.6\(2\)t1

Cisco>>Ios >> Version 15.6\(2\)t2

Cisco>>Ios >> Version 15.6\(3\)m

Cisco>>Ios >> Version 15.6\(3\)m0a

Cisco>>Ios >> Version 15.6\(3\)m1

Cisco>>Ios >> Version 15.6\(3\)m1a

Cisco>>Ios >> Version 15.6\(3\)m1b

Cisco>>Ios >> Version 15.6\(3\)sn

Cisco>>Ios >> Version 15.6\(4\)sn

Cisco>>Ios >> Version 15.6\(5\)sn

Cisco>>Ios >> Version 15.6\(6\)sn

Cisco>>Ios >> Version 15.6\(7\)sn

Cisco>>Ios_xe >> Version 3.2.0ja

Cisco>>Ios_xe >> Version 3.16.0as

Cisco>>Ios_xe >> Version 3.16.0bs

Cisco>>Ios_xe >> Version 3.16.0cs

Cisco>>Ios_xe >> Version 3.16.0s

Cisco>>Ios_xe >> Version 3.16.1as

Cisco>>Ios_xe >> Version 3.16.1s

Cisco>>Ios_xe >> Version 3.16.2as

Cisco>>Ios_xe >> Version 3.16.2bs

Cisco>>Ios_xe >> Version 3.16.2s

Cisco>>Ios_xe >> Version 3.16.3as

Cisco>>Ios_xe >> Version 3.16.3s

Cisco>>Ios_xe >> Version 3.16.4as

Cisco>>Ios_xe >> Version 3.16.4bs

Cisco>>Ios_xe >> Version 3.16.4cs

Cisco>>Ios_xe >> Version 3.16.4ds

Cisco>>Ios_xe >> Version 3.16.4es

Cisco>>Ios_xe >> Version 3.16.4gs

Cisco>>Ios_xe >> Version 3.16.4s

Cisco>>Ios_xe >> Version 3.16.5as

Cisco>>Ios_xe >> Version 3.16.5s

Cisco>>Ios_xe >> Version 3.17.0s

Cisco>>Ios_xe >> Version 3.17.1as

Cisco>>Ios_xe >> Version 3.17.1s

Cisco>>Ios_xe >> Version 3.17.3s

Cisco>>Ios_xe >> Version 3.17.4s

Cisco>>Ios_xe >> Version 3.18.0as

Cisco>>Ios_xe >> Version 3.18.0s

Cisco>>Ios_xe >> Version 3.18.0sp

Cisco>>Ios_xe >> Version 3.18.1asp

Cisco>>Ios_xe >> Version 3.18.1bsp

Cisco>>Ios_xe >> Version 3.18.1csp

Cisco>>Ios_xe >> Version 3.18.1gsp

Cisco>>Ios_xe >> Version 3.18.1hsp

Cisco>>Ios_xe >> Version 3.18.1isp

Cisco>>Ios_xe >> Version 3.18.1s

Cisco>>Ios_xe >> Version 3.18.1sp

Cisco>>Ios_xe >> Version 3.18.2asp

Cisco>>Ios_xe >> Version 3.18.2s

Cisco>>Ios_xe >> Version 3.18.2sp

Cisco>>Ios_xe >> Version 3.18.3s

Cisco>>Ios_xe >> Version 3.18.4s

Cisco>>Ios_xe >> Version 16.2.1

Cisco>>Ios_xe >> Version 16.2.2

Cisco>>Ios_xe >> Version 16.3.1

Cisco>>Ios_xe >> Version 16.3.1a

Cisco>>Ios_xe >> Version 16.3.2

Cisco>>Ios_xe >> Version 16.3.3

Cisco>>Ios_xe >> Version 16.3.4

Cisco>>Ios_xe >> Version 16.4.1

Cisco>>Ios_xe >> Version 16.4.2

Cisco>>Ios_xe >> Version 16.4.3

Cisco>>Ios_xe >> Version 16.5.1

Cisco>>Ios_xe >> Version 16.5.1a

Cisco>>Ios_xe >> Version 16.5.1b

Références

http://www.securityfocus.com/bid/107597
Tags : vdb-entry, x_refsource_BID