简体中文

CVE-2022-29277：详情

CVE-2022-29277

8.8
/
高危
0.05%V4
2022-11-15
00h00 +00:00
Overflow
Local
2025-04-30
14h56 +00:00
CVE.org
NVD
指定 CVE 通知
随时了解指定 CVE 的变更。
管理通知

CVE 描述

Incorrect pointer checks within the the FwBlockServiceSmm driver can allow arbitrary RAM modifications During review of the FwBlockServiceSmm driver, certain instances of SpiAccessLib could be tricked into writing 0xff to arbitrary system and SMRAM addresses. Fixed in: INTEL Purley-R: 05.21.51.0048 Whitley: 05.42.23.0066 Cedar Island: 05.42.11.0021 Eagle Stream: 05.44.25.0052 Greenlow/Greenlow-R(skylake/kabylake): Trunk Mehlow/Mehlow-R (CoffeeLake-S): Trunk Tatlow (RKL-S): Trunk Denverton: 05.10.12.0042 Snow Ridge: Trunk Graneville DE: 05.05.15.0038 Grangeville DE NS: 05.27.26.0023 Bakerville: 05.21.51.0026 Idaville: 05.44.27.0030 Whiskey Lake: Trunk Comet Lake-S: Trunk Tiger Lake H/UP3: 05.43.12.0052 Alder Lake: 05.44.23.0047 Gemini Lake: Not Affected Apollo Lake: Not Affected Elkhart Lake: 05.44.30.0018 AMD ROME: trunk MILAN: 05.36.10.0017 GENOA: 05.52.25.0006 Snowy Owl: Trunk R1000: 05.32.50.0018 R2000: 05.44.30.0005 V2000: Trunk V3000: 05.44.30.0007 Ryzen 5000: 05.44.30.0004 Embedded ROME: Trunk Embedded MILAN: Trunk Hygon Hygon #1/#2: 05.36.26.0016 Hygon #3: 05.44.26.0007 https://www.insyde.com/security-pledge/SA-2022060

CVE 信息

相关弱点

CWE-ID 弱点名称 来源
CWE-787 Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.

指标

指标 评分 严重程度 CVSS 向量 来源
V3.1 8.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

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.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

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.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

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.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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，其被利用的可能性高于 95% 的其他 CVE。因此，百分位可用于比较不同 CVE 的 EPSS 评分。
EPSS First.org

相关产品

配置 0

Amd>>Genoa_firmware >> Version 至（不含） 05.52.25.0006

Amd>>Genoa >> Version -

配置 0

Amd>>Hygon_1_firmware >> Version 至（不含） 05.36.26.0016

Amd>>Hygon_1 >> Version -

配置 0

Amd>>Hygon_2_firmware >> Version 至（不含） 05.36.26.0016

Amd>>Hygon_2 >> Version -

配置 0

Amd>>Hygon_3_firmware >> Version 至（不含） 05.44.26.0007

Amd>>Hygon_3 >> Version -

配置 0

Amd>>Milan_firmware >> Version 至（不含） 05.36.10.0017

Amd>>Milan >> Version -

配置 0

Amd>>Milan_firmware >> Version 至（不含） 05.36.26.0016

Amd>>Milan >> Version -

配置 0

Amd>>Rome_firmware >> Version 至（不含） 05.36.10.0017

Amd>>Rome >> Version -

配置 0

Amd>>Rome_firmware >> Version 至（不含） 05.36.26.0016

Amd>>Rome >> Version -

配置 0

Amd>>Ryzen_5300g_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5300g >> Version -

配置 0

Amd>>Ryzen_5300ge_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5300ge >> Version -

配置 0

Amd>>Ryzen_5600g_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5600g >> Version -

配置 0

Amd>>Ryzen_5600ge_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5600ge >> Version -

配置 0

Amd>>Ryzen_5600x_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5600x >> Version -

配置 0

Amd>>Ryzen_5700g_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5700g >> Version -

配置 0

Amd>>Ryzen_5700ge_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5700ge >> Version -

配置 0

Amd>>Ryzen_5800x_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5800x >> Version -

配置 0

Amd>>Ryzen_5800x3d_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5800x3d >> Version -

配置 0

Amd>>Ryzen_5900x_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5900x >> Version -

配置 0

Amd>>Ryzen_5950x_firmware >> Version 至（不含） 05.44.30.0004

Amd>>Ryzen_5950x >> Version -

配置 0

Amd>>Snowy_owl_r1000_firmware >> Version 至（不含） 05.32.50.0018

Amd>>Snowy_owl_r1000 >> Version -

配置 0

Amd>>Snowy_owl_r2000_firmware >> Version 至（不含） 05.44.30.0005

Amd>>Snowy_owl_r2000 >> Version -

配置 0

Amd>>Snowy_owl_v2000_firmware >> Version 至（不含） 05.44.30.0007

Amd>>Snowy_owl_v2000 >> Version -

配置 0

Amd>>Snowy_owl_v3000_firmware >> Version 至（不含） 05.44.30.0007

Amd>>Snowy_owl_v3000 >> Version -

配置 0

Intel>>Alder_lake_firmware >> Version 至（不含） 05.44.23.0047

Intel>>Alder_lake >> Version -

配置 0

Intel>>Bakerville_firmware >> Version 至（不含） 05.21.51.0026

Intel>>Bakerville >> Version -

配置 0

Intel>>Cedar_island_firmware >> Version 至（不含） 05.42.11.0021

Intel>>Cedar_island >> Version -

配置 0

Intel>>Idaville_firmware >> Version 至（不含） 05.43.12.0052

Intel>>Idaville >> Version -

配置 0

Intel>>Comet_lake-s_firmware >> Version 至（不含） 05.43.12.0052

Intel>>Comet_lake-s >> Version -

配置 0

Intel>>Tiger_lake_h\/up3_firmware >> Version 至（不含） 05.43.12.0052

Intel>>Tiger_lake_h\/up3 >> Version -

配置 0

Intel>>Whiskey_lake_firmware >> Version 至（不含） 05.43.12.0052

Intel>>Whiskey_lake >> Version -

配置 0

Intel>>Denverton_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Denverton >> Version -

配置 0

Intel>>Eagle_stream_firmware >> Version 至（不含） 05.44.25.0052

Intel>>Eagle_stream >> Version -

配置 0

Intel>>Grangeville_de_ns_firmware >> Version 至（不含） 05.27.26.0023

Intel>>Grangeville_de_ns >> Version -

配置 0

Intel>>Granville_de_firmware >> Version 至（不含） 05.05.15.0038

Intel>>Granville_de >> Version -

配置 0

Intel>>Greenlow_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Greenlow >> Version -

配置 0

Intel>>Greenlow-r_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Greenlow-r >> Version -

配置 0

Intel>>Mehlow_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Mehlow >> Version -

配置 0

Intel>>Mehlow-r_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Mehlow-r >> Version -

配置 0

Intel>>Tatlow_firmware >> Version 至（不含） 05.10.12.0042

Intel>>Tatlow >> Version -

配置 0

Intel>>Purley-r_firmware >> Version 至（不含） 05.21.51.0048

Intel>>Purley-r >> Version -

配置 0

Intel>>Whitley_firmware >> Version 至（不含） 05.42.23.0066

Intel>>Whitley >> Version -

参考资料

cvefind.com 上展示的信息来源于多个精心选择的权威数据源。CVE 数据由 MITRE Corporation 和 National Vulnerability Database (NVD) 提供。已知被利用漏洞（KEV）目录来源于 Cybersecurity and Infrastructure Security Agency (CISA)，EPSS 评分来自 FIRST.org。此外，软件弱点（CWE）和常见攻击模式（CAPEC）数据由 MITRE Corporation 维护，硬件和软件配置（CPE）信息由 NVD 提供。