CVE-2019-0069 : Detail

CVE-2019-0069

5.9
/
Medium
A02-Cryptographic Failures
0.04%V3
Local
2019-10-09
19h26 +00:00
2024-09-16
23h16 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: vSRX, SRX1500, SRX4K, ACX5K, EX4600, QFX5100, QFX5110, QFX5200, QFX10K and NFX Series: console management port device authentication credentials are logged in clear text

On EX4600, QFX5100 Series, NFX Series, QFX10K Series, QFX5110, QFX5200 Series, QFX5110, QFX5200, QFX10K Series, vSRX, SRX1500, SRX4000 Series, vSRX, SRX1500, SRX4000, QFX5110, QFX5200, QFX10K Series, when the user uses console management port to authenticate, the credentials used during device authentication are written to a log file in clear text. This issue does not affect users that are logging-in using telnet, SSH or J-web to the management IP. This issue affects ACX, NFX, SRX, EX and QFX platforms with the Linux Host OS architecture, it does not affect other SRX and EX platforms that do not use the Linux Host OS architecture. This issue affects Juniper Networks Junos OS: 15.1X49 versions prior to 15.1X49-D110 on vSRX, SRX1500, SRX4000 Series; 15.1X53 versions prior to 15.1X53-D234 on QFX5110, QFX5200 Series; 15.1X53 versions prior to 15.1X53-D68 on QFX10K Series; 17.1 versions prior to 17.1R2-S8, 17.1R3, on QFX5110, QFX5200, QFX10K Series; 17.2 versions prior to 17.2R1-S7, 17.2R2-S6, 17.2R3 on QFX5110, QFX5200, QFX10K Series; 17.3 versions prior to 17.3R2 on vSRX, SRX1500, SRX4000, QFX5110, QFX5200, QFX10K Series; 14.1X53 versions prior to 14.1X53-D47 on ACX5000, EX4600, QFX5100 Series; 15.1 versions prior to 15.1R7 on ACX5000, EX4600, QFX5100 Series; 16.1R7 versions prior to 16.1R7 on ACX5000, EX4600, QFX5100 Series; 17.1 versions prior to 17.1R2-S10, 17.1R3 on ACX5000, EX4600, QFX5100 Series; 17.2 versions prior to 17.2R3 on ACX5000, EX4600, QFX5100 Series; 17.3 versions prior to 17.3R3 on ACX5000, EX4600, QFX5100 Series; 17.4 versions prior to 17.4R2 on ACX5000, EX4600, QFX5100 Series; 18.1 versions prior to 18.1R2 on ACX5000, EX4600, QFX5100 Series; 15.1X53 versions prior to 15.1X53-D496 on NFX Series, 17.2 versions prior to 17.2R3-S1 on NFX Series; 17.3 versions prior to 17.3R3-S4 on NFX Series; 17.4 versions prior to 17.4R2-S4, 17.4R3 on NFX Series, 18.1 versions prior to 18.1R3-S4 on NFX Series; 18.2 versions prior to 18.2R2-S3, 18.2R3 on NFX Series; 18.3 versions prior to 18.3R1-S3, 18.3R2 on NFX Series; 18.4 versions prior to 18.4R1-S1, 18.4R2 on NFX Series.

CVE Solutions

For vSRX, SRX1500, SRX4000 Series, QFX5110, QFX5200, QFX10K Series: The following software releases have been updated to resolve this specific issue: 15.1X49-D110, 15.1X53-D234, 15.1X53-D68, 17.1R2-S8, 17.1R3, 17.2R1-S7, 17.2R2-S6, 17.2R3, 17.3R2, 17.4R1, and all subsequent releases. For ACX5000, EX4600 and QFX5100 Series: The following software releases have been updated to resolve this specific issue: 14.1X53-D47, 15.1R7, 16.1R7, 17.1R3, 17.2R3, 17.3R3, 17.4R2, 18.1R2, 18.2R1, and all subsequent releases. For NFX Series: The following software releases have been updated to resolve this specific issue: 15.1X53-D496, 17.2R3-S1, 17.3R3-S4, 17.4R3, 18.1R3-S4, 18.2R3, 18.3R2, 18.4R1-S1, 18.4R2, 19.1R1 and all subsequent releases. In addition to the upgrade, it is recommended to change the password and as the credentials might have been logged prior to the upgrade to the fixed release, in the SRX, QFX, ACX and EX Series it is recommended to clear the log files and archives.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-319 Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 5.9 MEDIUM CVSS:3.1/AV:L/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.

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.

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.
V3.1 5.5 MEDIUM CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.

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.

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.

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.

 [email protected]
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 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Srx1500 >> Version -

Juniper>>Srx4000 >> Version -

Juniper>>Vsrx >> Version -

Configuraton 0

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>>Qfx5110 >> Version -

Juniper>>Qfx5200 >> Version -

Configuraton 0

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>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Configuraton 0

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>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5200 >> Version -

Configuraton 0

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>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5200 >> Version -

Configuraton 0

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Qfx10008 >> Version -

Juniper>>Qfx10016 >> Version -

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5200 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx4000 >> Version -

Juniper>>Vsrx >> Version -

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

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>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

Juniper>>Junos >> Version 18.1

Juniper>>Acx5000 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Qfx5110 >> Version -

Configuraton 0

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

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>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

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>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

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>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

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>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Junos >> Version 18.2

Juniper>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Junos >> Version 18.3

Juniper>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

Configuraton 0

Juniper>>Junos >> Version 18.4

Juniper>>Junos >> Version 18.4

Juniper>>Nfx150 >> Version -

Juniper>>Nfx250 >> Version -

References

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