CVE 描述

Junos OS and Junos OS Evolved: PPMD goes into infinite loop upon receipt of malformed OSPF TLV

An Improper Check or Handling of Exceptional Conditions vulnerability in the processing of a malformed OSPF TLV in Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to cause the periodic packet management daemon (PPMD) process to go into an infinite loop, which in turn can cause protocols and functions reliant on PPMD such as OSPF neighbor reachability to be impacted, resulting in a sustained Denial of Service (DoS) condition. The DoS condition persists until the PPMD process is manually restarted. This issue affects: Juniper Networks Junos OS: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S5; 19.3 versions prior to 19.3R3-S3; 19.4 versions prior to 19.4R3-S9; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S1; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. Juniper Networks Junos OS Evolved: All versions prior to 20.4R3-S3-EVO; 21.1 versions prior to 21.1R2-EVO.

CVE 解決方案

The following software releases have been updated to resolve this specific issue: Junos OS: 19.1R3-S9, 19.2R3-S5, 19.3R3-S3, 19.4R3-S9, 20.1R3, 20.2R3-S1, 20.3R3, 20.4R3, 21.1R2, 21.2R1, and all subsequent releases. Junos OS Evolved: 20.4R3-S3-EVO, 21.1R2-EVO, 21.2R1-EVO, and all subsequent releases.

CVE 資訊

相關弱點

CWE-ID	弱點名稱	來源
CWE-703	Improper Check or Handling of Exceptional Conditions The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.

指標

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

EPSS

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

EPSS 評分

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

EPSS 百分位數

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

EPSS First.org

參考資料

https://kb.juniper.net/JSA69874
Tags : Vendor Advisory

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

日期	百分位
2022-10-23	27%
2023-02-19	28%
2023-03-12	11%
2023-08-06	1%
2023-08-13	11%
2023-09-03	1%
2023-09-10	11%
2023-12-03	1%
2023-12-10	11%
2023-12-24	1%
2024-03-03	11%
2024-03-24	16%
2024-04-14	17%
2024-06-02	19%
2024-06-08	2%
2024-08-25	21%
2024-09-01	2%
2024-09-08	21%
2024-12-15	22%
2024-12-22	14%
2025-01-12	15%
2025-01-19	15%
2025-03-18	21%
2025-04-15	25%
2025-07-13	27%
2025-08-08	26%
2025-08-14	28%
2025-10-14	27%
2025-10-15	28%
2025-10-19	42%
2025-10-21	48%
2025-11-09	29%
2025-11-12	3%
2025-11-16	29%
2025-11-18	25%
2025-11-21	3%
2025-11-23	29%
2025-12-03	3%
2025-12-04	29%
2025-12-10	3%
2026-01-20	29%
2026-05-10	28%
2026-05-31	29%
2026-06-07	28%
2026-06-14	29%

CVE-2022-22224

CVE 描述

Junos OS and Junos OS Evolved: PPMD goes into infinite loop upon receipt of malformed OSPF TLV

CVE 解決方案

CVE 資訊

相關弱點

指標

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

EPSS

EPSS 評分

EPSS 百分位數

相關產品

設定 0

設定 0

參考資料

CVE-2022-22224：詳細資料

CVE-2022-22224

CVE 描述

Junos OS and Junos OS Evolved: PPMD goes into infinite loop upon receipt of malformed OSPF TLV

CVE 解決方案

CVE 資訊

相關弱點

指標

Base: Exploitabilty Metrics

Base: Scope Metrics

Base: Impact Metrics

Temporal Metrics

Environmental Metrics

EPSS

EPSS 評分

EPSS 百分位數

相關產品

設定 0

設定 0

參考資料