CVE-2020-1631 Detail

CVE-2020-1631

Score / Severity

9.8

Critical

CVE Descriptions

Out of Cycle Security Advisory: Junos OS: Security vulnerability in J-Web and web based (HTTP/HTTPS) services

A vulnerability in the HTTP/HTTPS service used by J-Web, Web Authentication, Dynamic-VPN (DVPN), Firewall Authentication Pass-Through with Web-Redirect, and Zero Touch Provisioning (ZTP) allows an unauthenticated attacker to perform local file inclusion (LFI) or path traversal. Using this vulnerability, an attacker may be able to inject commands into the httpd.log, read files with 'world' readable permission file or obtain J-Web session tokens. In the case of command injection, as the HTTP service runs as user 'nobody', the impact of this command injection is limited. (CVSS score 5.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) In the case of reading files with 'world' readable permission, in Junos OS 19.3R1 and above, the unauthenticated attacker would be able to read the configuration file. (CVSS score 5.9, vector CVSS:3.1/ AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) If J-Web is enabled, the attacker could gain the same level of access of anyone actively logged into J-Web. If an administrator is logged in, the attacker could gain administrator access to J-Web. (CVSS score 8.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) This issue only affects Juniper Networks Junos OS devices with HTTP/HTTPS services enabled. Junos OS devices with HTTP/HTTPS services disabled are not affected. If HTTP/HTTPS services are enabled, the following command will show the httpd processes: user@device> show system processes | match http 5260 - S 0:00.13 /usr/sbin/httpd-gk -N 5797 - I 0:00.10 /usr/sbin/httpd --config /jail/var/etc/httpd.conf To summarize: If HTTP/HTTPS services are disabled, there is no impact from this vulnerability. If HTTP/HTTPS services are enabled and J-Web is not in use, this vulnerability has a CVSS score of 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N). If J-Web is enabled, this vulnerability has a CVSS score of 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Juniper SIRT has received a single report of this vulnerability being exploited in the wild. Out of an abundance of caution, we are notifying customers so they can take appropriate actions. Indicators of Compromise: The /var/log/httpd.log may have indicators that commands have injected or files being accessed. The device administrator can look for these indicators by searching for the string patterns "=*;*&" or "*%3b*&" in /var/log/httpd.log, using the following command: user@device> show log httpd.log | match "=*;*&|=*%3b*&" If this command returns any output, it might be an indication of malicious attempts or simply scanning activities. Rotated logs should also be reviewed, using the following command: user@device> show log httpd.log.0.gz | match "=*;*&|=*%3b*&" user@device> show log httpd.log.1.gz | match "=*;*&|=*%3b*&" Note that a skilled attacker would likely remove these entries from the local log file, thus effectively eliminating any reliable signature that the device had been attacked. This issue affects Juniper Networks Junos OS 12.3 versions prior to 12.3R12-S16; 12.3X48 versions prior to 12.3X48-D101, 12.3X48-D105; 14.1X53 versions prior to 14.1X53-D54; 15.1 versions prior to 15.1R7-S7; 15.1X49 versions prior to 15.1X49-D211, 15.1X49-D220; 16.1 versions prior to 16.1R7-S8; 17.2 versions prior to 17.2R3-S4; 17.3 versions prior to 17.3R3-S8; 17.4 versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R2-S7, 18.2R3-S4; 18.3 versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions prior to 18.4R1-S7, 18.4R3-S2 ; 18.4 version 18.4R2 and later versions; 19.1 versions prior to 19.1R1-S5, 19.1R3-S1; 19.1 version 19.1R2 and later versions; 19.2 versions prior to 19.2R2; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S2, 19.4R2; 20.1 versions prior to 20.1R1-S1, 20.1R2.

CVE Solutions

The following software releases have been updated to resolve this specific issue: 12.3R12-S16, 12.3X48-D101, 12.3X48-D105, 14.1X53-D54, 15.1X49-D211, 15.1X49-D220, 15.1R7-S7, 16.1R7-S8, 17.2R3-S4, 17.4R2-S11, 17.3R3-S8, 17.4R3-S2, 18.1R3-S10, 18.2R2-S7, 18.2R3-S4, 18.3R2-S4, 18.3R3-S2, 18.4R1-S7, 18.4R3-S2, 19.1R1-S5, 19.1R3-S1, 19.2R2, 19.3R2-S3, 19.3R3, 19.4R1-S2, 19.4R2, 20.1R1-S1, 20.1R2 and all subsequent releases. Note: At the time of this publication, the following fixed releases are available for customer download: 12.3X48-D101, 15.1X49-D211, 18.2R3-S4, 18.4R3-S2, and 20.1R1-S1, the remaining fixed releases will be available in future time. 12.3X48-D101 & 15.1X49-D211 releases can be downloaded from the below URLs: 12.3X48-D101 : Branch SRX-Series Install Package (for SRX100H2, SRX110HE2, SRX210H2, SRX220H2, SRX240H2, SRX550, SRX650): junos-srxsme-12.3X48-D101-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107438.html MD5 = b822376f7a385e74499b186cf28c122b SHA-1 = e6138e45bf9d29e962468e6e114e537142d4cc0d SHA-256 = b21a9ae9f5d0b0ec25180682193faba7bf54e836fda0eb78babd3df843f90e6a SRX 1000/3000-Series Install Package : junos-srx1k3k-12.3X48-D101-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107436.html MD5 = b93229ea43f66b539f22ecc5a9be0f07 SHA-1 = 2c625e9bc155b9fcb4c9a1a371bba473363ee6f0 SHA-256 = 982434f9cde9492e1d80d14c43a7cdcc5261db15a11f65fa7c9881a0fc0cd3db SRX5000-Series Install Package: junos-srx5000-12.3X48-D101-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107437.html MD5 = 7dc73801b7680fda42d453d6d3d6f10c SHA-1 = 05f1eda5ec112c7e2afeebea4d47c007e0a8bd60 SHA-256 = 88d40e4b6b949a5c656c2b5fffa3adb41fe4943fb3e5d9cfaa439e603889e839 15.1X49-D211: SRX300 & SRX500-Series Install Package: junos-srxsme-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107439.html MD5 = dfd3428c7f83eb11142bbe32bac2a151 SHA-1 = a22f0ead795c8afb0a4d59d1b9b785c83801cd65 SHA-256 = dc42e24db0e2af7b2e6aaafdaa61f8e658fabc91c8a888efad586a5fbd2fa29a SRX1500 Install Package: junos-srxentedge-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107442.html MD5 = 348f2fcd96b31d51b9d71147d09fabd8 SHA-1 = cf8ee775ca1ca12706975fdd0748c1967732c2fe SHA-256 = 62d460ea531161936f0ac75fa4501bc6cadb700388bdb93b7e706a09e985eff5 SRX4100 and SRX4200 Install Package: junos-srxmr-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107441.html MD5 = 55b4c96b05b5fd9595a8ee071dbbf438 SHA-1 = ae6d7978964c3be6b632033b3616208e47653617 SHA-256 = 20274c3b66d4b54471684a5f534abe0ba1d8bebabbb6f78f0028fcc275076df1 SRX5000 Series Install Package: junos-srx5000-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107440.html MD5 = b918fa5a341815ccdb230560539e8725 SHA-1 = 38e912a55f1407e18e1bb8305f854fcd97c1adcb SHA-256 = c1aaafdd9b23a525236c414e4cf213542246326317070b5e98ac5cccc5fa1e72 vSRX Upgrade TGZ: junos-vsrx-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107452.html MD5 = 55b4c96b05b5fd9595a8ee071dbbf438 SHA-1 = ae6d7978964c3be6b632033b3616208e47653617 SHA-256 = 20274c3b66d4b54471684a5f534abe0ba1d8bebabbb6f78f0028fcc275076df1

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-22	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-73	External Control of File Name or Path The product allows user input to control or influence paths or file names that are used in filesystem operations.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V3.1	8.8	HIGH	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. 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. 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. 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. 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.
V3.1	9.8	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. 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. 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]

CISA KEV (Known Exploited Vulnerabilities)

Vulnerability name : Juniper Junos OS Path Traversal Vulnerability

Required action : Apply updates per vendor instructions.

Known To Be Used in Ransomware Campaigns : Unknown

Added : 2022-03-24 23h00 +00:00

Action is due : 2022-04-14 22h00 +00:00

Important information

This CVE is identified as vulnerable and poses an active threat, according to the Catalog of Known Exploited Vulnerabilities (CISA KEV). The CISA has listed this vulnerability as actively exploited by cybercriminals, emphasizing the importance of taking immediate action to address this flaw. It is imperative to prioritize the update and remediation of this CVE to protect systems against potential cyberattacks.

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 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3

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

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53 (Open CPE detail)