CVE-2020-11899 : Chi tiết

CVE-2020-11899

5.4
/
Trung bình
35.27%V4
2020-06-17
10h27 +00:00
Overflow
Adjacent
2025-10-21
23h35 +00:00
Thông báo cho một CVE
Luôn được thông báo về mọi thay đổi đối với một CVE cụ thể.
Quản lý thông báo

Mô tả CVE

The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.

Thông tin CVE

Điểm yếu liên quan

CWE-ID Tên điểm yếu Nguồn
CWE-125 Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.

Số liệu

Số liệu Điểm Mức độ nghiêm trọng CVSS Vector Nguồn
V3.1 5.4 MEDIUM CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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.

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 limited. 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.

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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
V2 4.8 AV:A/AC:L/Au:N/C:N/I:P/A:P nvd@nist.gov

CISA KEV (Lỗ hổng đã bị khai thác đã biết)

Tên lỗ hổng : Treck TCP/IP stack Out-of-Bounds Read Vulnerability

Hành động bắt buộc : Apply updates per vendor instructions.

Được biết là sử dụng trong các chiến dịch Ransomware : Unknown

Đã thêm : 2022-03-03 00h00 +00:00

Hành động đến hạn : 2022-03-17 00h00 +00:00

Thông tin quan trọng
CVE này được xác định là dễ bị tấn công và đặt ra mối đe dọa tích cực, theo Danh mục lỗ hổng đã bị khai thác đã biết (CISA KEV). CISA đã liệt kê lỗ hổng này là đang bị tội phạm mạng khai thác tích cực, nhấn mạnh tầm quan trọng của việc hành động ngay lập tức để giải quyết lỗ hổng này. Cần ưu tiên cập nhật và khắc phục CVE này để bảo vệ hệ thống khỏi các cuộc tấn công mạng tiềm ẩn.

EPSS

EPSS là mô hình tính điểm dự đoán khả năng một lỗ hổng bị khai thác.

Điểm EPSS

Mô hình EPSS tạo ra điểm xác suất từ 0 đến 1 (0 đến 100%). Điểm càng cao, xác suất một lỗ hổng bị khai thác càng lớn.

Phân vị EPSS

Phân vị được dùng để xếp hạng CVE theo điểm EPSS. Ví dụ, một CVE ở phân vị thứ 95 theo điểm EPSS có nhiều khả năng bị khai thác hơn 95% CVE khác. Do đó, phân vị được dùng để so sánh điểm EPSS của một CVE với các CVE khác.

Sản phẩm được đề cập

Cấu hình 0

Treck>>Tcp\/ip >> Version Đến (không bao gồm) 6.0.1.66

Cấu hình 0

Dell>>Wyse_5050_all-in-one_firmware >> Version -

Dell>>Wyse_5050_all-in-one >> Version -

Cấu hình 0

Dell>>Wyse_7030_firmware >> Version -

Dell>>Wyse_7030 >> Version -

Cấu hình 0

Dell>>Wyse_5030_firmware >> Version -

Dell>>Wyse_5030 >> Version -

Tài liệu tham khảo

https://www.treck.com
Tags : x_refsource_MISC
https://www.kb.cert.org/vuls/id/257161
Tags : third-party-advisory, x_refsource_CERT-VN