extensive" and review the output. See further details below. An example output is: show interfaces extensive | match policer Policer: Input: __default_arp_policer__ <<< incorrect if user ARP Policer was applied on an AE interface and the default ARP Policer is displayed Policer: Input: jtac-arp-ae5.317-inet-arp <<< correct if user ARP Policer was applied on an AE interface For all platforms, except SRX Series: This issue affects Juniper Networks Junos OS: All versions 5.6R1 and all later versions prior to 18.4 versions prior to 18.4R2-S9, 18.4R3-S9 with the exception of 15.1 versions 15.1R7-S10 and later versions; 19.4 versions prior to 19.4R3-S3; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S2; 20.3 version 20.3R1 and later versions; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2; This issue does not affect Juniper Networks Junos OS versions prior to 5.6R1. On SRX Series this issue affects Juniper Networks Junos OS: 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.4 versions prior to 19.4R3-S4; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S2; 20.3 version 20.3R1 and later versions; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. This issue does not affect 18.4 versions prior to 18.4R1 on SRX Series. This issue does not affect Junos OS Evolved.">

CVE-2021-0289 : Detail

CVE-2021-0289

6.5
/
Medium
0.06%V3
Adjacent
2021-07-15
20h01 +00:00
2024-09-17
03h48 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: User-defined ARP Policer isn't applied on Aggregated Ethernet (AE) interface until firewall process is restarted

When user-defined ARP Policer is configured and applied on one or more Aggregated Ethernet (AE) interface units, a Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability between the Device Control Daemon (DCD) and firewall process (dfwd) daemons of Juniper Networks Junos OS allows an attacker to bypass the user-defined ARP Policer. In this particular case the User ARP policer is replaced with default ARP policer. To review the desired ARP Policers and actual state one can run the command "show interfaces <> extensive" and review the output. See further details below. An example output is: show interfaces extensive | match policer Policer: Input: __default_arp_policer__ <<< incorrect if user ARP Policer was applied on an AE interface and the default ARP Policer is displayed Policer: Input: jtac-arp-ae5.317-inet-arp <<< correct if user ARP Policer was applied on an AE interface For all platforms, except SRX Series: This issue affects Juniper Networks Junos OS: All versions 5.6R1 and all later versions prior to 18.4 versions prior to 18.4R2-S9, 18.4R3-S9 with the exception of 15.1 versions 15.1R7-S10 and later versions; 19.4 versions prior to 19.4R3-S3; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S2; 20.3 version 20.3R1 and later versions; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2; This issue does not affect Juniper Networks Junos OS versions prior to 5.6R1. On SRX Series this issue affects Juniper Networks Junos OS: 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.4 versions prior to 19.4R3-S4; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S2; 20.3 version 20.3R1 and later versions; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. This issue does not affect 18.4 versions prior to 18.4R1 on SRX Series. This issue does not affect Junos OS Evolved.

CVE Solutions

The following software releases have been updated to resolve this specific issue: For all platforms, except SRX Series, using Junos OS 15.1R7-S10, 18.4R2-S9, 18.4R3-S9, 19.4R3-S4, 20.1R3, 20.2R3-S2, 20.4R3, 21.1R2, 21.2R1, and all subsequent releases. On SRX series using Junos OS 18.4R2-S9, 18.4R3-S9, 19.4R3-S4. 20.1R3, 20.4R3, 21.1R2, 21.2R1, and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state.

Metrics

Metrics Score Severity CVSS Vector Source
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.
V3.1 5.3 MEDIUM CVSS:3.1/AV:A/AC:H/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.

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.

 [email protected]
V2 2.9 AV:A/AC:M/Au:N/C:N/I:N/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.
EPSS First.org

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version From (including) 5.7 To (excluding) 15.1

Juniper>>Junos >> Version From (including) 15.2 To (excluding) 18.4

Juniper>>Junos >> Version 5.6

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 18.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.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.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 21.1

Juniper>>Acx1000 >> Version -

Juniper>>Acx1100 >> Version -

Juniper>>Acx2000 >> Version -

Juniper>>Acx2100 >> Version -

Juniper>>Acx2200 >> Version -

Juniper>>Acx4000 >> Version -

Juniper>>Acx500 >> Version -

Juniper>>Acx5000 >> Version -

Juniper>>Acx5048 >> Version -

Juniper>>Acx5096 >> Version -

Juniper>>Acx5400 >> Version -

Juniper>>Acx5448 >> Version -

Juniper>>Acx5800 >> Version -

Juniper>>Acx6300 >> Version -

Juniper>>Acx6360 >> Version -

Juniper>>Acx710 >> Version -

Juniper>>Atp400 >> Version -

Juniper>>Atp700 >> Version -

Juniper>>Csrx >> Version -

Juniper>>Ctp150 >> Version -

Juniper>>Ctp2008 >> Version -

Juniper>>Ctp2024 >> Version -

Juniper>>Ctp2056 >> Version -

Juniper>>Dx >> Version -

Juniper>>Dx >> Version 5.1

Juniper>>Ex_rps >> Version -

Juniper>>Ex2200 >> Version -

Juniper>>Ex2200-c >> Version -

Juniper>>Ex2200-vc >> Version -

Juniper>>Ex2300 >> Version -

Juniper>>Ex2300-c >> Version -

Juniper>>Ex2300m >> Version -

Juniper>>Ex3200 >> Version -

Juniper>>Ex3300 >> Version -

Juniper>>Ex3300-vc >> Version -

Juniper>>Ex3400 >> Version -

Juniper>>Ex4200 >> Version -

Juniper>>Ex4200-vc >> Version -

Juniper>>Ex4300 >> Version -

Juniper>>Ex4300-24p >> Version -

Juniper>>Ex4300-24p-s >> Version -

Juniper>>Ex4300-24t >> Version -

Juniper>>Ex4300-24t-s >> Version -

Juniper>>Ex4300-32f >> Version -

Juniper>>Ex4300-32f-dc >> Version -

Juniper>>Ex4300-32f-s >> Version -

Juniper>>Ex4300-48mp >> Version -

Juniper>>Ex4300-48mp-s >> Version -

Juniper>>Ex4300-48p >> Version -

Juniper>>Ex4300-48p-s >> Version -

Juniper>>Ex4300-48t >> Version -

Juniper>>Ex4300-48t-afi >> Version -

Juniper>>Ex4300-48t-dc >> Version -

Juniper>>Ex4300-48t-dc-afi >> Version -

Juniper>>Ex4300-48t-s >> Version -

Juniper>>Ex4300-48tafi >> Version -

Juniper>>Ex4300-48tdc >> Version -

Juniper>>Ex4300-48tdc-afi >> Version -

Juniper>>Ex4300-mp >> Version -

Juniper>>Ex4300-vc >> Version -

Juniper>>Ex4300m >> Version -

Juniper>>Ex4400 >> Version -

Juniper>>Ex4500 >> Version -

Juniper>>Ex4500-vc >> Version -

Juniper>>Ex4550 >> Version -

Juniper>>Ex4550-vc >> Version -

Juniper>>Ex4550\/vc >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Ex4600-vc >> Version -

Juniper>>Ex4650 >> Version -

Juniper>>Ex6200 >> Version -

Juniper>>Ex6210 >> Version -

Juniper>>Ex8200 >> Version -

Juniper>>Ex8200-vc >> Version -

Juniper>>Ex8208 >> Version -

Juniper>>Ex8216 >> Version -

Juniper>>Ex9200 >> Version -

Juniper>>Ex9204 >> Version -

Juniper>>Ex9208 >> Version -

Juniper>>Ex9214 >> Version -

Juniper>>Ex9250 >> Version -

Juniper>>Ex9251 >> Version -

Juniper>>Ex9253 >> Version -

Juniper>>Fips_infranet_controller_6500 >> Version -

Juniper>>Fips_secure_access_4000 >> Version -

Juniper>>Fips_secure_access_4500 >> Version -

Juniper>>Fips_secure_access_6000 >> Version -

Juniper>>Fips_secure_access_6500 >> Version -

Juniper>>Gfx3600 >> Version -

Juniper>>Idp250 >> Version -

Juniper>>Idp75 >> Version -

Juniper>>Idp800 >> Version -

Juniper>>Idp8200 >> Version -

Juniper>>Infranet_controller_4000 >> Version -

Juniper>>Infranet_controller_4500 >> Version -

Juniper>>Infranet_controller_6000 >> Version -

Juniper>>Infranet_controller_6500 >> Version -

Juniper>>Jatp >> Version 400

Juniper>>Jatp >> Version 700

Juniper>>Junos >> Version -

Juniper>>Junos_space_ja1500_appliance >> Version -

Juniper>>Junos_space_ja2500_appliance >> Version -

Juniper>>Ln1000 >> Version -

Juniper>>Ln2600 >> Version -

Juniper>>M10i >> Version -

Juniper>>M120 >> Version -

Juniper>>M320 >> Version -

Juniper>>M7i >> Version -

Juniper>>Mag2600_gateway >> Version -

Juniper>>Mag4610_gateway >> Version -

Juniper>>Mag6610_gateway >> Version -

Juniper>>Mag6611_gateway >> Version -

Juniper>>Mx >> Version -

Juniper>>Mx10 >> Version -

Juniper>>Mx10000 >> Version -

Juniper>>Mx10003 >> Version -

Juniper>>Mx10008 >> Version -

Juniper>>Mx10016 >> Version -

Juniper>>Mx104 >> Version -

Juniper>>Mx150 >> Version -

Juniper>>Mx2008 >> Version -

Juniper>>Mx2010 >> Version -

Juniper>>Mx2020 >> Version -

Juniper>>Mx204 >> Version -

Juniper>>Mx240 >> Version -

Juniper>>Mx40 >> Version -

Juniper>>Mx480 >> Version -

Juniper>>Mx5 >> Version -

Juniper>>Mx80 >> Version -

Juniper>>Mx960 >> Version -

Juniper>>Netscreen-5200 >> Version -

Juniper>>Netscreen-5400 >> Version -

Juniper>>Netscreen-5gt >> Version -

Juniper>>Netscreen-5gt >> Version 5.0

Juniper>>Netscreen-idp >> Version 3.0

Juniper>>Netscreen-idp >> Version 3.0r1

Juniper>>Netscreen-idp >> Version 3.0r2

Juniper>>Netscreen-idp_10 >> Version -

Juniper>>Netscreen-idp_100 >> Version -

Juniper>>Netscreen-idp_1000 >> Version -

Juniper>>Netscreen-idp_500 >> Version -

Juniper>>Nfx >> Version -

Juniper>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Juniper>>Nfx350 >> Version -

Juniper>>Nsm3000 >> Version -

Juniper>>Nsmexpress >> Version -

Juniper>>Ocx1100 >> Version -

Juniper>>Ptx1000 >> Version -

Juniper>>Ptx1000-72q >> Version -

Juniper>>Ptx10000 >> Version -

Juniper>>Ptx10001 >> Version -

Juniper>>Ptx10001-36mr >> Version -

Juniper>>Ptx100016 >> Version -

Juniper>>Ptx10002 >> Version -

Juniper>>Ptx10002-60c >> Version -

Juniper>>Ptx10003 >> Version -

Juniper>>Ptx10003_160c >> Version -

Juniper>>Ptx10003_80c >> Version -

Juniper>>Ptx10003_81cd >> Version -

Juniper>>Ptx10004 >> Version -

Juniper>>Ptx10008 >> Version -

Juniper>>Ptx10016 >> Version -

Juniper>>Ptx3000 >> Version -

Juniper>>Ptx5000 >> Version -

Juniper>>Qfx10000 >> Version -

Juniper>>Qfx10002 >> Version -

Juniper>>Qfx10002-32q >> Version -

Juniper>>Qfx10002-60c >> Version -

Juniper>>Qfx10002-72q >> Version -

Juniper>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx3000-g >> Version -

Juniper>>Qfx3000-m >> Version -

Juniper>>Qfx3008-i >> Version -

Juniper>>Qfx3100 >> Version -

Juniper>>Qfx3500 >> Version -

Juniper>>Qfx3600 >> Version -

Juniper>>Qfx3600-i >> Version -

Juniper>>Qfx5100 >> Version -

Juniper>>Qfx5100-96s >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5120 >> Version -

Juniper>>Qfx5130 >> Version -

Juniper>>Qfx5200 >> Version -

Juniper>>Qfx5200-32c >> Version -

Juniper>>Qfx5200-48y >> Version -

Juniper>>Qfx5210 >> Version -

Juniper>>Qfx5210-64c >> Version -

Juniper>>Qfx5220 >> Version -

Juniper>>Router_m10 >> Version -

Juniper>>Router_m16 >> Version -

Juniper>>Router_m20 >> Version -

Juniper>>Router_m40 >> Version -

Juniper>>Router_m5 >> Version -

Juniper>>Secure_access_2000 >> Version -

Juniper>>Secure_access_2500 >> Version -

Juniper>>Secure_access_4000 >> Version -

Juniper>>Secure_access_4500 >> Version -

Juniper>>Secure_access_6000 >> Version -

Juniper>>Secure_access_6500 >> Version -

Juniper>>Secure_access_700 >> Version -

Juniper>>T1600 >> Version -

Juniper>>T320 >> Version -

Juniper>>T4000 >> Version -

Juniper>>T640 >> Version -

Juniper>>Xre200 >> Version -

Configuraton 0

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 18.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.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.4

Juniper>>Junos >> Version 20.4

Juniper>>Junos >> Version 21.1

Juniper>>Srx100 >> Version -

Juniper>>Srx110 >> Version -

Juniper>>Srx1400 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx210 >> Version -

Juniper>>Srx220 >> Version -

Juniper>>Srx240 >> Version -

Juniper>>Srx240h2 >> Version -

Juniper>>Srx300 >> Version -

Juniper>>Srx320 >> Version -

Juniper>>Srx340 >> Version -

Juniper>>Srx3400 >> Version -

Juniper>>Srx345 >> Version -

Juniper>>Srx3600 >> Version -

Juniper>>Srx380 >> Version -

Juniper>>Srx4000 >> Version -

Juniper>>Srx4100 >> Version -

Juniper>>Srx4200 >> Version -

Juniper>>Srx4600 >> Version -

Juniper>>Srx5000 >> Version -

Juniper>>Srx5400 >> Version -

Juniper>>Srx550 >> Version -

Juniper>>Srx550_hm >> Version -

Juniper>>Srx550m >> Version -

Juniper>>Srx5600 >> Version -

Juniper>>Srx5800 >> Version -

Juniper>>Srx650 >> Version -

References

https://kb.juniper.net/JSA11191
Tags : x_refsource_CONFIRM