CVE-2019-1758
00h20 +00:00
CVE 설명
Cisco IOS Software Catalyst 6500 Series 802.1x Authentication Bypass Vulnerability
A vulnerability in 802.1x function of Cisco IOS Software on the Catalyst 6500 Series Switches could allow an unauthenticated, adjacent attacker to access the network prior to authentication. The vulnerability is due to how the 802.1x packets are handled in the process path. An attacker could exploit this vulnerability by attempting to connect to the network on an 802.1x configured port. A successful exploit could allow the attacker to intermittently obtain access to the network.CVE 정보
관련 약점
| 약점 이름 | 출처 | |
|---|---|---|
| Improper Authentication When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
메트릭
| 메트릭 | 점수 | 심각도 | CVSS 벡터 | 출처 |
|---|---|---|---|---|
| V3.0 | 4.7 | MEDIUM |
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
추가 정보
Base: Exploitabilty MetricsThe 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 MetricsAn 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 MetricsThe 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 MetricsThe 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 |
|
| 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 MetricsThe 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 MetricsAn 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 MetricsThe 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 MetricsThe 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 |
nvd@nist.gov |
| V2 | 3.3 | AV:A/AC:L/Au:N/C:N/I:P/A:N | nvd@nist.gov |
EPSS
EPSS 점수
EPSS 백분위수
언급된 제품
구성 0
Cisco>>Ios >> Version 12.2\(33\)sxj6
Cisco>>Ios >> Version 12.2\(33\)sxj7
Cisco>>Ios >> Version 12.2\(33\)sxj8
Cisco>>Ios >> Version 12.2\(33\)sxj9
Cisco>>Ios >> Version 12.2\(33\)sxj10
Cisco>>Ios >> Version 12.2\(60\)ez12
Cisco>>Ios >> Version 15.1\(1\)sy1
Cisco>>Ios >> Version 15.1\(1\)sy2
Cisco>>Ios >> Version 15.1\(1\)sy3
Cisco>>Ios >> Version 15.1\(1\)sy4
Cisco>>Ios >> Version 15.1\(1\)sy5
Cisco>>Ios >> Version 15.1\(1\)sy6
Cisco>>Ios >> Version 15.1\(2\)sg8a
Cisco>>Ios >> Version 15.1\(2\)sy
Cisco>>Ios >> Version 15.1\(2\)sy1
Cisco>>Ios >> Version 15.1\(2\)sy2
Cisco>>Ios >> Version 15.1\(2\)sy3
Cisco>>Ios >> Version 15.1\(2\)sy4
Cisco>>Ios >> Version 15.1\(2\)sy4a
Cisco>>Ios >> Version 15.1\(2\)sy5
Cisco>>Ios >> Version 15.1\(2\)sy6
Cisco>>Ios >> Version 15.1\(2\)sy7
Cisco>>Ios >> Version 15.1\(2\)sy8
Cisco>>Ios >> Version 15.1\(2\)sy9
Cisco>>Ios >> Version 15.1\(2\)sy10
Cisco>>Ios >> Version 15.1\(2\)sy11
Cisco>>Ios >> Version 15.1\(2\)sy12
Cisco>>Ios >> Version 15.1\(2\)sy13
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\)svp1
Cisco>>Ios >> Version 15.1\(3\)svp2
Cisco>>Ios >> Version 15.1\(4\)m12c
Cisco>>Ios >> Version 15.2\(1\)sy
Cisco>>Ios >> Version 15.2\(1\)sy0a
Cisco>>Ios >> Version 15.2\(1\)sy1
Cisco>>Ios >> Version 15.2\(1\)sy1a
Cisco>>Ios >> Version 15.2\(1\)sy2
Cisco>>Ios >> Version 15.2\(1\)sy3
Cisco>>Ios >> Version 15.2\(1\)sy4
Cisco>>Ios >> Version 15.2\(1\)sy5
Cisco>>Ios >> Version 15.2\(1\)sy6
Cisco>>Ios >> Version 15.2\(1\)sy7
Cisco>>Ios >> Version 15.2\(2\)sy
Cisco>>Ios >> Version 15.2\(2\)sy1
Cisco>>Ios >> Version 15.2\(2\)sy2
Cisco>>Ios >> Version 15.2\(2\)sy3
Cisco>>Ios >> Version 15.2\(3\)ea1
Cisco>>Ios >> Version 15.2\(4\)jn1
Cisco>>Ios >> Version 15.2\(4a\)ea5
Cisco>>Ios >> Version 15.3\(0\)sy
Cisco>>Ios >> Version 15.3\(1\)sy
Cisco>>Ios >> Version 15.3\(1\)sy1
Cisco>>Ios >> Version 15.3\(1\)sy2
Cisco>>Ios >> Version 15.3\(3\)ja1n
Cisco>>Ios >> Version 15.3\(3\)jf35
Cisco>>Ios >> Version 15.3\(3\)ji2
Cisco>>Ios >> Version 15.4\(1\)sy
Cisco>>Ios >> Version 15.4\(1\)sy1
Cisco>>Ios >> Version 15.4\(1\)sy2
Cisco>>Ios >> Version 15.4\(1\)sy3
Cisco>>Ios >> Version 15.4\(1\)sy4
Cisco>>Ios >> Version 15.5\(1\)sy
Cisco>>Ios >> Version 15.5\(1\)sy1
Cisco>>Ios >> Version 15.5\(1\)sy2
Cisco>>Ios >> Version 15.6\(2\)sp3b
참고 자료
Tags : vendor-advisory, x_refsource_CISCO
