CVE-2022-1434 : Chi tiết

CVE-2022-1434

5.9
/
Trung bình
0.07%V4
2022-05-03
15h15 +00:00
A02-Cryptographic Failures
Network
2026-10-14
12h43 +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

Incorrect MAC key used in the RC4-MD5 ciphersuite

The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is 1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).

Thông tin CVE

Điểm yếu liên quan

CWE-ID Tên điểm yếu Nguồn
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.

Số liệu

Số liệu Điểm Mức độ nghiêm trọng CVSS Vector Nguồn
V3.1 5.9 MEDIUM CVSS:3.1/AV:N/AC:H/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.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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
V2 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N nvd@nist.gov

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

Openssl>>Openssl >> Version Từ (bao gồm) 3.0.0 Đến (không bao gồm) 3.0.3

Cấu hình 0

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Clustered_data_ontap >> Version -

Netapp>>Clustered_data_ontap_antivirus_connector >> Version -

Netapp>>Santricity_smi-s_provider >> Version -

Netapp>>Smi-s_provider >> Version -

Netapp>>Snapmanager >> Version -

Netapp>>Solidfire\,_enterprise_sds_\&_hci_storage_node >> Version -

Netapp>>Solidfire_\&_hci_management_node >> Version -

Cấu hình 0

Netapp>>A700s_firmware >> Version -

Netapp>>A700s >> Version -

Cấu hình 0

Netapp>>H300s_firmware >> Version -

Netapp>>H300s >> Version -

Cấu hình 0

Netapp>>H500s_firmware >> Version -

Netapp>>H500s >> Version -

Cấu hình 0

Netapp>>H700s_firmware >> Version -

Netapp>>H700s >> Version -

Cấu hình 0

Netapp>>H300e_firmware >> Version -

Netapp>>H300e >> Version -

Cấu hình 0

Netapp>>H500e_firmware >> Version -

Netapp>>H500e >> Version -

Cấu hình 0

Netapp>>H700e_firmware >> Version -

Netapp>>H700e >> Version -

Cấu hình 0

Netapp>>H410s_firmware >> Version -

Netapp>>H410s >> Version -

Cấu hình 0

Netapp>>Aff_8300_firmware >> Version -

Netapp>>Aff_8300 >> Version -

Cấu hình 0

Netapp>>Fas_8300_firmware >> Version -

Netapp>>Fas_8300 >> Version -

Cấu hình 0

Netapp>>Aff_8700_firmware >> Version -

Netapp>>Aff_8700 >> Version -

Cấu hình 0

Netapp>>Fas_8700_firmware >> Version -

Netapp>>Fas_8700 >> Version -

Cấu hình 0

Netapp>>Aff_a400_firmware >> Version -

Netapp>>Aff_a400 >> Version -

Cấu hình 0

Netapp>>Fabric-attached_storage_a400_firmware >> Version -

Netapp>>Fabric-attached_storage_a400 >> Version -

Cấu hình 0

Netapp>>A250_firmware >> Version -

Netapp>>A250 >> Version -

Cấu hình 0

Netapp>>Aff_500f_firmware >> Version -

Netapp>>Aff_500f >> Version -

Cấu hình 0

Netapp>>Fas_500f_firmware >> Version -

Netapp>>Fas_500f >> Version -

Tài liệu tham khảo