CVE-2020-22656 : 상세 정보

CVE-2020-22656

7.5
/
높음
0.25%V4
2023-01-20
00h00 +00:00
Network
2025-04-03
18h01 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

In Ruckus R310 10.5.1.0.199, Ruckus R500 10.5.1.0.199, Ruckus R600 10.5.1.0.199, Ruckus T300 10.5.1.0.199, Ruckus T301n 10.5.1.0.199, Ruckus T301s 10.5.1.0.199, SmartCell Gateway 200 (SCG200) before 3.6.2.0.795, SmartZone 100 (SZ-100) before 3.6.2.0.795, SmartZone 300 (SZ300) before 3.6.2.0.795, Virtual SmartZone (vSZ) before 3.6.2.0.795, ZoneDirector 1100 9.10.2.0.130, ZoneDirector 1200 10.2.1.0.218, ZoneDirector 3000 10.2.1.0.218, ZoneDirector 5000 10.0.1.0.151, a vulnerability allows attackers to make the Secure Boot in failed attempts state (rfwd).

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE Other 정보 없음.
CWE-1272 Sensitive Information Uncleared Before Debug/Power State Transition
The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 7.5 HIGH CVSS:3.1/AV:N/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.

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.

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

EPSS

EPSS는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.

EPSS 점수

EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.

EPSS 백분위수

백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.

언급된 제품

구성 0

Ruckuswireless>>R310_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R310 >> Version -

구성 0

Ruckuswireless>>R500_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R500 >> Version -

구성 0

Ruckuswireless>>R600_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R600 >> Version -

구성 0

Ruckuswireless>>T300_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T300 >> Version -

구성 0

Ruckuswireless>>T301n_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T301n >> Version -

구성 0

Ruckuswireless>>T301s_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T301s >> Version -

구성 0

Ruckuswireless>>Scg200_firmware >> Version 까지 (미포함) 3.6.2.0.795

Ruckuswireless>>Scg200 >> Version -

구성 0

Ruckuswireless>>Sz-100_firmware >> Version 까지 (미포함) 3.6.2.0.795

Ruckuswireless>>Sz-100 >> Version -

구성 0

Ruckuswireless>>Sz-300_firmware >> Version 까지 (미포함) 3.6.2.0.795

Ruckuswireless>>Sz-300 >> Version -

구성 0

Ruckuswireless>>Vsz_firmware >> Version 까지 (미포함) 3.6.2.0.795

Ruckuswireless>>Vsz >> Version -

구성 0

Ruckuswireless>>Zonedirector_1100_firmware >> Version 9.10.2.0.130

Ruckuswireless>>Zonedirector_1100 >> Version -

구성 0

Ruckuswireless>>Zonedirector_1200_firmware >> Version 10.2.1.0.218

Ruckuswireless>>Zonedirector_1200 >> Version -

구성 0

Ruckuswireless>>Zonedirector_3000_firmware >> Version 10.2.1.0.218

Ruckuswireless>>Zonedirector_3000 >> Version -

구성 0

Ruckuswireless>>Zonedirector_5000_firmware >> Version 10.0.1.0.151

Ruckuswireless>>Zonedirector_5000 >> Version -

참고 자료