CVE-2021-21973:詳細資料

CVE-2021-21973

5.3
/
中危
90.39%V4
2021-02-24
16h42 +00:00
Server-Side Request Forgery - SSRF
A10-Server-Side Req. Forgery (SSRF)
Network
2025-10-21
23h25 +00:00
指定 CVE 通知
掌握特定 CVE 的任何變更。
管理通知

CVE 描述

The vSphere Client (HTML5) contains an SSRF (Server Side Request Forgery) vulnerability due to improper validation of URLs in a vCenter Server plugin. A malicious actor with network access to port 443 may exploit this issue by sending a POST request to vCenter Server plugin leading to information disclosure. This affects: VMware vCenter Server (7.x before 7.0 U1c, 6.7 before 6.7 U3l and 6.5 before 6.5 U3n) and VMware Cloud Foundation (4.x before 4.2 and 3.x before 3.10.1.2).

CVE 資訊

相關弱點

CWE-ID 弱點名稱 來源
CWE-918 Server-Side Request Forgery
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

指標

指標 評分 嚴重程度 CVSS 向量 來源
V3.1 5.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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.

None

There is no loss of integrity within 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 5 AV:N/AC:L/Au:N/C:P/I:N/A:N nvd@nist.gov

CISA KEV(已知被利用漏洞)

漏洞名稱 : VMware vCenter Server and Cloud Foundation Server Side Request Forgery (SSRF) Vulnerability

必要行動 : Apply updates per vendor instructions.

已知用於勒索軟體活動 : Unknown

新增日期 : 2022-03-07 00h00 +00:00

行動截止日期 : 2022-03-21 00h00 +00:00

重要資訊
根據已知被利用漏洞目錄(CISA KEV),此 CVE 已被識別為存在漏洞且構成主動威脅。CISA 已將此漏洞列為網路犯罪者正在積極利用的目標,強調立即採取行動修補此缺陷的重要性。必須優先更新和修復此 CVE,以保護系統免受潛在網路攻擊。

EPSS

EPSS 是一種預測漏洞被利用可能性的評分模型。

EPSS 評分

EPSS 模型產生介於 0 到 1(0% 到 100%)之間的概率分數。分數越高,漏洞被利用的概率越大。

EPSS 百分位數

百分位數用於根據 EPSS 分數對 CVE 進行排名。例如,EPSS 評分在第 95 百分位的 CVE 比 95% 的其他 CVE 更有可能被利用。因此,百分位數用於比較某 CVE 的 EPSS 分數與其他 CVE 的相對位置。

相關產品

設定 0

Vmware>>Cloud_foundation >> Version 從(含) 3.0 至(不含) 3.10.1.2

Vmware>>Cloud_foundation >> Version 從(含) 4.0 至(不含) 4.2

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.5

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 6.7

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

Vmware>>Vcenter_server >> Version 7.0

參考資料