CVE 描述

A buffer overflow in the SystemBootManagerDxe driver in some Lenovo Notebook products may allow an attacker with local privileges to execute arbitrary code.

CVE 解决方案

Update system firmware to the version (or newer) indicated for your model in the product Impact section of LEN-91369

CVE 信息

相关弱点

CWE-ID	弱点名称	来源
CWE-122	Heap-based Buffer Overflow The product writes past the end of a buffer that was allocated on the heap.
CWE-120	Buffer Copy without Checking Size of Input The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

指标

指标	评分	严重程度	CVSS 向量	来源
V3.1	6.7	MEDIUM	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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. High The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files. 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. 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.
V3.1	7.8	HIGH	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. 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. 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

参考资料

https://support.lenovo.com/us/en/product_security/LEN-91369
Tags : Vendor Advisory

日期	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2023-01-29	–	–	1.04%	–	–
2023-03-12	–	–	–	0.04%	–
2024-02-11	–	–	–	0.04%	–
2024-06-02	–	–	–	0.04%	–
2025-01-19	–	–	–	0.04%	–
2025-03-18	–	–	–	–	0.05%
2025-04-15	–	–	–	–	0.05%
2025-07-14	–	–	–	–	0.04%
2025-08-17	–	–	–	–	0.04%
2025-08-21	–	–	–	–	0.04%
2025-10-03	–	–	–	–	0.04%
2025-10-04	–	–	–	–	0.04%
2025-10-09	–	–	–	–	0.04%
2025-10-12	–	–	–	–	0.04%
2025-10-15	–	–	–	–	0.04%
2025-10-18	–	–	–	–	0.04%
2025-11-18	–	–	–	–	0.04%
2025-11-19	–	–	–	–	0.04%
2025-11-20	–	–	–	–	0.04%
2025-11-21	–	–	–	–	0.05%
2025-11-23	–	–	–	–	0.05%
2025-11-25	–	–	–	–	0.07%
2025-12-04	–	–	–	–	0.1%
2025-12-05	–	–	–	–	0.09%
2026-02-22	–	–	–	–	0.04%
2026-05-31	–	–	–	–	0.04%

日期	百分位
2023-01-29	43%
2023-03-12	6%
2024-02-11	5%
2024-06-02	5%
2025-01-19	5%
2025-03-18	11%
2025-04-15	14%
2025-07-14	1%
2025-08-17	9%
2025-08-21	1%
2025-10-03	11%
2025-10-04	1%
2025-10-09	11%
2025-10-12	1%
2025-10-15	11%
2025-10-18	13%
2025-11-18	7%
2025-11-19	8%
2025-11-20	9%
2025-11-21	15%
2025-11-23	14%
2025-11-25	22%
2025-12-04	28%
2025-12-05	27%
2026-02-22	13%
2026-05-31	14%

CVE-2022-1892：详情

CVE-2022-1892

CVE 描述

CVE 解决方案

CVE 信息

相关弱点

指标

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

EPSS

EPSS 评分

EPSS 百分位

相关产品

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0

配置 0