CVE-2020-22656 : Detail

CVE-2020-22656

7.5
/
Tinggi
0.25%V4
2023-01-20
00h00 +00:00
Network
2025-04-03
18h01 +00:00
Notifikasi untuk CVE tertentu
Tetap terinformasi tentang perubahan untuk CVE tertentu.
Kelola notifikasi

Deskripsi 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).

Informasi CVE

Kelemahan Terkait

CWE-ID Nama Kelemahan Sumber
CWE Other Tidak ada informasi.
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.

Metrik

Metrik Skor Tingkat keparahan CVSS Vektor Sumber
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 adalah model penilaian yang memprediksi kemungkinan suatu kerentanan dieksploitasi.

Skor EPSS

Model EPSS menghasilkan skor probabilitas antara 0 dan 1 (0 hingga 100%). Semakin tinggi skor, semakin besar probabilitas bahwa suatu kerentanan akan dieksploitasi.

Persentil EPSS

Persentil digunakan untuk meranking CVE berdasarkan skor EPSS mereka. Misalnya, CVE di persentil ke-95 berdasarkan skor EPSS-nya lebih mungkin dieksploitasi daripada 95% CVE lainnya. Dengan demikian, persentil digunakan untuk membandingkan skor EPSS suatu CVE dengan CVE lainnya.

Produk yang Disebutkan

Konfigurasi 0

Ruckuswireless>>R310_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R310 >> Version -

Konfigurasi 0

Ruckuswireless>>R500_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R500 >> Version -

Konfigurasi 0

Ruckuswireless>>R600_firmware >> Version 10.5.1.0.199

Ruckuswireless>>R600 >> Version -

Konfigurasi 0

Ruckuswireless>>T300_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T300 >> Version -

Konfigurasi 0

Ruckuswireless>>T301n_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T301n >> Version -

Konfigurasi 0

Ruckuswireless>>T301s_firmware >> Version 10.5.1.0.199

Ruckuswireless>>T301s >> Version -

Konfigurasi 0

Ruckuswireless>>Scg200_firmware >> Version Hingga (tidak termasuk) 3.6.2.0.795

Ruckuswireless>>Scg200 >> Version -

Konfigurasi 0

Ruckuswireless>>Sz-100_firmware >> Version Hingga (tidak termasuk) 3.6.2.0.795

Ruckuswireless>>Sz-100 >> Version -

Konfigurasi 0

Ruckuswireless>>Sz-300_firmware >> Version Hingga (tidak termasuk) 3.6.2.0.795

Ruckuswireless>>Sz-300 >> Version -

Konfigurasi 0

Ruckuswireless>>Vsz_firmware >> Version Hingga (tidak termasuk) 3.6.2.0.795

Ruckuswireless>>Vsz >> Version -

Konfigurasi 0

Ruckuswireless>>Zonedirector_1100_firmware >> Version 9.10.2.0.130

Ruckuswireless>>Zonedirector_1100 >> Version -

Konfigurasi 0

Ruckuswireless>>Zonedirector_1200_firmware >> Version 10.2.1.0.218

Ruckuswireless>>Zonedirector_1200 >> Version -

Konfigurasi 0

Ruckuswireless>>Zonedirector_3000_firmware >> Version 10.2.1.0.218

Ruckuswireless>>Zonedirector_3000 >> Version -

Konfigurasi 0

Ruckuswireless>>Zonedirector_5000_firmware >> Version 10.0.1.0.151

Ruckuswireless>>Zonedirector_5000 >> Version -

Referensi