CVE-2019-1690 : Détail

CVE-2019-1690

6.5
/
Moyen
A01-Broken Access Control
0.11%V4
Adjacent
2019-03-11
22h00 +00:00
2024-11-21
19h42 +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 Application Policy Infrastructure Controller IPv6 Link-Local Address Vulnerability

A vulnerability in the management interface of Cisco Application Policy Infrastructure Controller (APIC) software could allow an unauthenticated, adjacent attacker to gain unauthorized access on an affected device. The vulnerability is due to a lack of proper access control mechanisms for IPv6 link-local connectivity imposed on the management interface of an affected device. An attacker on the same physical network could exploit this vulnerability by attempting to connect to the IPv6 link-local address on the affected device. A successful exploit could allow the attacker to bypass default access control restrictions on an affected device. Cisco Application Policy Infrastructure Controller (APIC) devices running versions prior to 4.2(0.21c) are affected.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-284 Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 6.5 MEDIUM CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within 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.

 nvd@nist.gov
V3.0 4.3 MEDIUM CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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

A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router).

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.

Unchanged

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

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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within 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 that one has in the description of a vulnerability.

Environmental Metrics
V2 3.3 AV:A/AC:L/Au:N/C:N/I:P/A:N nvd@nist.gov

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>>Application_policy_infrastructure_controller >> Version To (excluding) 4.2\(0.21c\)

Cisco>>Firepower_2110 >> Version -

Cisco>>Firepower_2120 >> Version -

Cisco>>Firepower_2130 >> Version -

Cisco>>Firepower_2140 >> Version -

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

Cisco>>Mds_9134 >> Version -

Cisco>>Mds_9509 >> Version -

Cisco>>Mds_9710 >> Version -

Cisco>>Nexus_3016 >> Version -

Cisco>>Nexus_3048 >> Version -

Cisco>>Nexus_3064 >> Version -

Cisco>>Nexus_3064-t >> Version -

Cisco>>Nexus_31108pc-v >> Version -

Cisco>>Nexus_31108tc-v >> Version -

Cisco>>Nexus_31128pq >> Version -

Cisco>>Nexus_3132c-z >> Version -

Cisco>>Nexus_3132q >> Version -

Cisco>>Nexus_3132q-v >> Version -

Cisco>>Nexus_3132q-xl >> Version -

Cisco>>Nexus_3164q >> Version -

Cisco>>Nexus_3172 >> Version -

Cisco>>Nexus_3172pq-xl >> Version -

Cisco>>Nexus_3172tq >> Version -

Cisco>>Nexus_3172tq-32t >> 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 >> Version -

Cisco>>Nexus_3524-x >> Version -

Cisco>>Nexus_3524-xl >> Version -

Cisco>>Nexus_3548 >> Version -

Cisco>>Nexus_3548-x >> Version -

Cisco>>Nexus_3548-xl >> Version -

Cisco>>Nexus_36180yc-r >> Version -

Cisco>>Nexus_3636c-r >> Version -

Cisco>>Nexus_5010 >> Version -

Cisco>>Nexus_5020 >> Version -

Cisco>>Nexus_5548p >> Version -

Cisco>>Nexus_5548up >> Version -

Cisco>>Nexus_5596t >> Version -

Cisco>>Nexus_5596up >> Version -

Cisco>>Nexus_56128p >> Version -

Cisco>>Nexus_5624q >> Version -

Cisco>>Nexus_5648q >> Version -

Cisco>>Nexus_5672up >> Version -

Cisco>>Nexus_5696q >> Version -

Cisco>>Nexus_7000 >> Version -

Cisco>>Nexus_7700 >> Version -

Cisco>>Nexus_9000v >> 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_93120tx >> Version -

Cisco>>Nexus_93128tx >> Version -

Cisco>>Nexus_93180lc-ex >> Version -

Cisco>>Nexus_93180yc-ex >> Version -

Cisco>>Nexus_93180yc-fx >> Version -

Cisco>>Nexus_93216tc-fx2 >> Version -

Cisco>>Nexus_93240yc-fx2 >> Version -

Cisco>>Nexus_9332c >> Version -

Cisco>>Nexus_9332pq >> Version -

Cisco>>Nexus_93360yc-fx2 >> Version -

Cisco>>Nexus_9336c-fx2 >> Version -

Cisco>>Nexus_9336pq_aci_spine >> Version -

Cisco>>Nexus_9348gc-fxp >> Version -

Cisco>>Nexus_9364c >> Version -

Cisco>>Nexus_9372px >> Version -

Cisco>>Nexus_9372px-e >> Version -

Cisco>>Nexus_9372tx >> Version -

Cisco>>Nexus_9372tx-e >> Version -

Cisco>>Nexus_9396px >> Version -

Cisco>>Nexus_9396tx >> Version -

Cisco>>Nexus_9504 >> Version -

Cisco>>Nexus_9508 >> Version -

Cisco>>Nexus_9516 >> Version -

Cisco>>Ucs_6248up >> Version -

Cisco>>Ucs_6296up >> Version -

Cisco>>Ucs_6324 >> Version -

Cisco>>Ucs_6332 >> Version -

Cisco>>Ucs_6400 >> Version -

Références

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