CVE-2021-0220 : Detail

CVE-2021-0220

6.8
/
Medium
A04-Insecure Design
0.28%V4
Network
2021-01-15
17h36 +00:00
2024-09-16
22h20 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos Space: Shared secrets stored in recoverable format and directly exposed through the UI

The Junos Space Network Management Platform has been found to store shared secrets in a recoverable format that can be exposed through the UI. An attacker who is able to execute arbitrary code in the victim browser (for example via XSS) or access cached contents may be able to obtain a copy of credentials managed by Junos Space. The impact of a successful attack includes, but is not limited to, obtaining access to other servers connected to the Junos Space Management Platform. This issue affects Juniper Networks Junos Space versions prior to 20.3R1.

CVE Solutions

The following software releases have been updated to resolve these specific issues: Junos Space 20.3R1, and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-257 Storing Passwords in a Recoverable Format
The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts.
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.

Metrics

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

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.

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.

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.

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 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N nvd@nist.gov

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_space >> Version 1.0

Juniper>>Junos_space >> Version 1.1

Juniper>>Junos_space >> Version 1.2

Juniper>>Junos_space >> Version 1.3

Juniper>>Junos_space >> Version 1.4

Juniper>>Junos_space >> Version 2.0

Juniper>>Junos_space >> Version 11.1

Juniper>>Junos_space >> Version 11.2

Juniper>>Junos_space >> Version 11.3

Juniper>>Junos_space >> Version 11.4

Juniper>>Junos_space >> Version 12.1

Juniper>>Junos_space >> Version 12.2

Juniper>>Junos_space >> Version 12.3

Juniper>>Junos_space >> Version 13.1

Juniper>>Junos_space >> Version 13.1

Juniper>>Junos_space >> Version 13.3

Juniper>>Junos_space >> Version 14.1

Juniper>>Junos_space >> Version 15.1

Juniper>>Junos_space >> Version 15.1

Juniper>>Junos_space >> Version 15.1

Juniper>>Junos_space >> Version 15.2

Juniper>>Junos_space >> Version 16.1

Juniper>>Junos_space >> Version 17.1

Juniper>>Junos_space >> Version 17.2

Juniper>>Junos_space >> Version 17.2

Juniper>>Junos_space >> Version 18.1

Juniper>>Junos_space >> Version 18.1r1

Juniper>>Junos_space >> Version 18.2

Juniper>>Junos_space >> Version 18.3

Juniper>>Junos_space >> Version 18.4

Juniper>>Junos_space >> Version 19.1

Juniper>>Junos_space >> Version 15.1

Juniper>>Junos_space >> Version 15.2

Juniper>>Junos_space >> Version 16.1

Juniper>>Junos_space >> Version 17.2

Juniper>>Junos_space >> Version 18.1

Juniper>>Junos_space >> Version 18.2

Juniper>>Junos_space >> Version 18.3

Juniper>>Junos_space >> Version 18.4

Juniper>>Junos_space >> Version 19.1

Juniper>>Junos_space >> Version 19.2

Juniper>>Junos_space >> Version 19.3

Juniper>>Junos_space >> Version 19.4

Juniper>>Junos_space >> Version 20.1

References

https://kb.juniper.net/JSA11110
Tags : x_refsource_CONFIRM
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.