English
Français
Light
Dark
System

CVEFind - Alertes CVE

Restez informé en continue
Créer un compte Ouvrez un compte Simple et Gratuit Se connecter Gérez vos alertes

CVE-2021-0247 : Détail

CVE-2021-0247

5.5
/
MEDIUM
0.07%V3
Network
2021-04-13 22:00 +00:00
2024-08-03 15:32 +00:00
CVE.org
NVD

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.
Gestion des alertes

Descriptions

Junos OS: PTX Series, QFX Series: Due to a race condition input loopback firewall filters applied to interfaces may not operate even when listed in the running configuration.

A Race Condition (Concurrent Execution using Shared Resource with Improper Synchronization) vulnerability in the firewall process (dfwd) of Juniper Networks Junos OS allows an attacker to bypass the firewall rule sets applied to the input loopback filter on any interfaces of a device. This issue is detectable by reviewing the PFE firewall rules, as well as the firewall counters and seeing if they are incrementing or not. For example: show firewall Filter: __default_bpdu_filter__ Filter: FILTER-INET-01 Counters: Name Bytes Packets output-match-inet 0 0 <<<<<< missing firewall packet count This issue affects: Juniper Networks Junos OS 14.1X53 versions prior to 14.1X53-D53 on QFX Series; 14.1 versions 14.1R1 and later versions prior to 15.1 versions prior to 15.1R7-S6 on QFX Series, PTX Series; 15.1X53 versions prior to 15.1X53-D593 on QFX Series; 16.1 versions prior to 16.1R7-S7 on QFX Series, PTX Series; 16.2 versions prior to 16.2R2-S11, 16.2R3 on QFX Series, PTX Series; 17.1 versions prior to 17.1R2-S11, 17.1R3-S2 on QFX Series, PTX Series; 17.2 versions prior to 17.2R1-S9, 17.2R3-S3 on QFX Series, PTX Series; 17.3 versions prior to 17.3R2-S5, 17.3R3-S7 on QFX Series, PTX Series; 17.4 versions prior to 17.4R2-S9, 17.4R3 on QFX Series, PTX Series; 18.1 versions prior to 18.1R3-S9 on QFX Series, PTX Series; 18.2 versions prior to 18.2R2-S6, 18.2R3-S3 on QFX Series, PTX Series; 18.3 versions prior to 18.3R1-S7, 18.3R2-S3, 18.3R3-S1 on QFX Series, PTX Series; 18.4 versions prior to 18.4R1-S5, 18.4R2-S3, 18.4R2-S7, 18.4R3 on QFX Series, PTX Series; 19.1 versions prior to 19.1R1-S4, 19.1R2-S1, 19.1R3 on QFX Series, PTX Series; 19.2 versions prior to 19.2R1-S3, 19.2R2 on QFX Series, PTX Series.

Solutions

The following software releases have been updated to resolve this specific issue: Junos OS 14.1X53-D53, 15.1R7-S6, 15.1X53-D593, 16.1R7-S7, 16.2R2-S11, 16.2R3, 17.1R2-S11, 17.1R3-S2, 17.2R1-S9, 17.2R3-S3, 17.3R2-S5, 17.3R3-S7, 17.4R2-S9, 17.4R3, 18.1R3-S9, 18.2R2-S6, 18.2R3-S3, 18.3R1-S7, 18.3R2-S3, 18.3R3-S1, 18.4R1-S5, 18.4R2-S3, 18.4R3, 19.1R1-S4, 19.1R2-S1, 19.1R3, 19.2R1-S3, 19.2R2, 19.3R1, and all subsequent releases.

Informations

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently.

Metrics

Metric Score Sévérité CVSS Vecteur Source
V3.1 5.1 MEDIUM CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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.

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.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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 5.5 MEDIUM CVSS:3.1/AV:N/AC:H/PR:H/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.

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.

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.

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

EPSS

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

EPSS Score

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.

EPSS Percentile

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 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Qfx10002 >> Version -

Juniper>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx5100 >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5120 >> Version -

Juniper>>Qfx5130 >> Version -

Juniper>>Qfx5200 >> Version -

Juniper>>Qfx5210 >> Version -

Juniper>>Qfx5220 >> Version -

Configuraton 0

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

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.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 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.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 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>>Ptx1000 >> Version -

Juniper>>Ptx10001-36mr >> Version -

Juniper>>Ptx10002 >> Version -

Juniper>>Ptx10003 >> Version -

Juniper>>Ptx10004 >> Version -

Juniper>>Ptx10008 >> Version -

Juniper>>Ptx10016 >> Version -

Juniper>>Ptx3000 >> Version -

Juniper>>Ptx5000 >> Version -

Juniper>>Qfx10002 >> Version -

Juniper>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx5100 >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5120 >> Version -

Juniper>>Qfx5130 >> Version -

Juniper>>Qfx5200 >> Version -

Juniper>>Qfx5210 >> Version -

Juniper>>Qfx5220 >> Version -

References

https://kb.juniper.net/JSA11140
Tags : x_refsource_MISC

Plus d'informations
Cliquez sur le bouton à gauche (OFF), pour autoriser l'inscription de cookie améliorant les fonctionnalités du site. Cliquez sur le bouton à gauche (Tout accepter), pour ne plus autoriser l'inscription de cookie améliorant les fonctionnalités du site.