CVE-2021-31382 : Detail

CVE-2021-31382

9
/
Critical
0.14%V3
Network
2021-10-19
18h17 +00:00
2024-09-17
01h05 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: PTX1000 System, PTX10002-60C System: After upgrading, configured firewall filters may be applied on incorrect interfaces

On PTX1000 System, PTX10002-60C System, after upgrading to an affected release, a Race Condition vulnerability between the chassis daemon (chassisd) and firewall process (dfwd) of Juniper Networks Junos OS, may update the device's interfaces with incorrect firewall filters. This issue only occurs when upgrading the device to an affected version of Junos OS. Interfaces intended to have protections may have no protections assigned to them. Interfaces with one type of protection pattern may have alternate protections assigned to them. Interfaces intended to have no protections may have protections assigned to them. These firewall rule misassignments may allow genuine traffic intended to be stopped at the interface to propagate further, potentially causing disruptions in services by propagating unwanted traffic. An attacker may be able to take advantage of these misassignments. This issue affects Juniper Networks Junos OS on PTX1000 System: 17.2 versions 17.2R1 and later versions prior to 17.3 versions prior to 17.3R3-S12; 17.4 versions prior to 17.4R3-S5; 18.1 versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R1-S8, 18.4R2-S8, 18.4R3-S8; 19.1 versions prior to 19.1R3-S5; 19.2 versions prior to 19.2R3-S2; 19.3 versions prior to 19.3R2-S6, 19.3R3-S3; 19.4 versions prior to 19.4R2-S4, 19.4R3-S3; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2-S1, 20.3R3; 20.4 versions prior to 20.4R1-S1, 20.4R2. This issue does not affect Juniper Networks Junos OS prior to version 17.2R1 on PTX1000 System. This issue affects Juniper Networks Junos OS on PTX10002-60C System: 18.2 versions 18.2R1 and later versions prior to 18.4 versions prior to 18.4R3-S9; 19.1 versions later than 19.1R1 prior to 19.4 versions prior to 19.4R2-S5, 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions 20.4R1 and later versions prior to 21.1 versions prior to 21.1R2; 21.2 versions 21.2R1 and later versions prior to 21.3 versions prior to 21.3R2. This issue does not affect Juniper Networks Junos OS prior to version 18.2R1 on PTX10002-60C System. This issue impacts all filter families (inet, inet6, etc.) and all loopback filters. It does not rely upon the location where a filter is set, impacting both logical and physical interfaces.

CVE Solutions

The following software releases have been updated to resolve this specific issue: Junos OS on PTX1000 System: 17.3R3-S12, 18.1R3-S13, 18.2R3-S8, 18.3R3-S5, 18.4R1-S8, 18.4R2-S8, 18.4R3-S8, 19.1R3-S5, 19.2R3-S2, 19.3R2-S6, 19.3R3-S3, 19.4R2-S4, 19.4R3-S3, 20.1R3, 20.2R2-S3, 20.2R3, 20.3R2-S1, 20.3R3, 20.4R1-S1, 20.4R2, 21.1R1, and all subsequent releases. Junos OS on PTX10002-60C System: 18.4R3-S9, 19.4R2-S5, 19.4R3-S5, 20.1R3-S1, 20.2R3-S2, 20.3R3-S1, 21.1R2, 21.3R2, 21.4R1, and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 6.5 MEDIUM CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

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.

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.

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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.

V3.1 9 CRITICAL CVSS:3.1/AV:N/AC:H/PR:N/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.

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.

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.

[email protected]
V2 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.1

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.4

Juniper>>Ptx1000 >> Version -

Configuraton 0

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75

Juniper>>Junos >> Version 18.2x75-d10

Juniper>>Junos >> Version 18.2x75-d30

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.1

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.2

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.3

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 19.4

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.1

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.2

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.3

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.1

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.2

Juniper>>Junos >> Version 21.3

Juniper>>Ptx10002-60c >> Version -

References

https://kb.juniper.net/JSA11250
Tags : x_refsource_CONFIRM
https://kb.juniper.net/KB10956
Tags : x_refsource_MISC