CVE-2021-0263 Détail

Descriptions du CVE

Junos OS: PTX Series: Denial of Service in packet processing due to heavy route churn when J-Flow sampling is enabled

A Data Processing vulnerability in the Multi-Service process (multi-svcs) on the FPC of Juniper Networks Junos OS on the PTX Series routers may lead to the process becoming unresponsive, ultimately affecting traffic forwarding, allowing an attacker to cause a Denial of Service (DoS) condition . The Multi-Service Process running on the FPC is responsible for handling sampling-related operations when a J-Flow configuration is activated. This can occur during periods of heavy route churn, causing the Multi-Service Process to stop processing updates, without consuming any further updates from kernel. This back pressure towards the kernel affects further dynamic updates from other processes in the system, including RPD, causing a KRT-STUCK condition and traffic forwarding issues. An administrator can monitor the following command to check if there is the KRT queue is stuck: user@device > show krt state ... Number of async queue entries: 65007 <--- this value keep on increasing. The following logs/alarms will be observed when this condition exists: user@junos> show chassis alarms 2 alarms currently active Alarm time Class Description 2020-10-11 04:33:45 PDT Minor Potential slow peers are: MSP(FPC1-PIC0) MSP(FPC3-PIC0) MSP(FPC4-PIC0) Logs: Oct 11 04:33:44.672 2020 test /kernel: rts_peer_cp_recv_timeout : Bit set for msp8 as it is stuck Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: Error in parsing composite nexthop Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: composite nexthop parsing error Oct 11 04:43:05 2020 test /kernel: rt_pfe_veto: Possible slowest client is msp38. States processed - 65865741. States to be processed - 0 Oct 11 04:55:55 2020 test /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8311787520) Current delayed unref = (60000), Current unique delayed unref = (10896), Max delayed unref on this platform = (40000) Current delayed weight unref = (71426) Max delayed weight unref on this platform= (400000) curproc = rpd Oct 11 04:56:00 2020 test /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2 This issue only affects PTX Series devices. No other products or platforms are affected by this vulnerability. This issue affects Juniper Networks Junos OS on PTX Series: 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S8, 18.4R3-S7; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S2, 20.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 18.2R1.

Solutions du CVE

The following software releases have been updated to resolve this specific issue: Junos OS 18.2R3-S7, 18.3R3-S4, 18.4R2-S8, 18.4R3-S7, 19.1R3-S4, 19.2R3-S1, 19.3R3-S1, 19.4R2-S4, 19.4R3-S1, 20.1R2, 20.2R2, 20.3R1-S2, 20.3R2, 20.4R1, and all subsequent releases.

Informations du CVE

Faiblesses connexes

CWE-ID	Nom de la faiblesse	Source
CWE-19	Category : Data Processing Errors Weaknesses in this category are typically found in functionality that processes data. Data processing is the manipulation of input to retrieve or save information.
CWE Other	No informations.

Métriques

Métriques	Score	Gravité	CVSS Vecteur	Source
V3.1	5.9	MEDIUM	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H More informations 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. 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.
V2	4.3		AV:N/AC:M/Au:N/C:N/I:N/A:P	[email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

EPSS First.org

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)
Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3 (Open CPE detail)