CVE-2020-1688 Detail

CVE Descriptions

Junos OS: SRX and NFX Series: Insufficient Web API private key protection

On Juniper Networks SRX Series and NFX Series, a local authenticated user with access to the shell may obtain the Web API service private key that is used to provide encrypted communication between the Juniper device and the authenticator services. Exploitation of this vulnerability may allow an attacker to decrypt the communications between the Juniper device and the authenticator service. This Web API service is used for authentication services such as the Juniper Identity Management Service, used to obtain user identity for Integrated User Firewall feature, or the integrated ClearPass authentication and enforcement feature. This issue affects Juniper Networks Junos OS on Networks SRX Series and NFX Series: 12.3X48 versions prior to 12.3X48-D105; 15.1X49 versions prior to 15.1X49-D190; 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; 18.1 versions prior to 18.1R3-S7; 18.2 versions prior to 18.2R3; 18.3 versions prior to 18.3R2-S4, 18.3R3; 18.4 versions prior to 18.4R1-S7, 18.4R2; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S4, 19.2R2.

CVE Solutions

The following software releases have been updated to resolve this specific issue: Junos OS 12.3X48-D105, 15.1X49-D190, 16.1R7-S8, 17.2R3-S4, 17.3R3-S8, 17.4R2-S11, 17.4R3, 18.1R3-S7, 18.2R3, 18.3R2-S4, 18.3R3, 18.4R1-S7, 18.4R2, 18.4R3, 19.1R2, 19.2R1-S4, 19.2R2, 19.3R1, and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-359	Exposure of Private Personal Information to an Unauthorized Actor The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
CWE-522	Insufficiently Protected Credentials The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-320	Category : Key Management Errors Weaknesses in this category are related to errors in the management of cryptographic keys.
CWE Other	No informations.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V3.1	6.5	MEDIUM	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N 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. Local The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. 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. Low The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources. 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. 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. None There is no impact to availability within 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.
V2	2.1		AV:L/AC:L/Au:N/C:P/I:N/A:N	[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 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)