CVE-2018-0024 : Detail

CVE-2018-0024

7.8
/
High
Improper Privilege Management
A04-Insecure Design
0.05%V3
Local
2018-07-11
18h00 +00:00
2024-09-16
16h28 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: A privilege escalation vulnerability exists where authenticated users with shell access can become root

An Improper Privilege Management vulnerability in a shell session of Juniper Networks Junos OS allows an authenticated unprivileged attacker to gain full control of the system. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D45 on SRX Series; 12.3X48 versions prior to 12.3X48-D20 on SRX Series; 12.3 versions prior to 12.3R11 on EX Series; 14.1X53 versions prior to 14.1X53-D30 on EX2200/VC, EX3200, EX3300/VC, EX4200, EX4300, EX4550/VC, EX4600, EX6200, EX8200/VC (XRE), QFX3500, QFX3600, QFX5100;; 15.1X49 versions prior to 15.1X49-D20 on SRX Series.

CVE Solutions

The following software releases have been updated to resolve this specific issue: Junos OS 12.1X46-D45, 12.3X48-D20, 12.3R11, 14.1X53-D30, 15.1X49-D20 and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-269 Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 7.8 HIGH CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

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 against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker is authorized with (i.e. 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 may have the ability to cause an impact only to non-sensitive resources.

User Interaction

This metric captures the requirement for a 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

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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 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 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 that one has in the description of a vulnerability.

Environmental Metrics
V2 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C [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.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Srx100 >> Version -

Juniper>>Srx110 >> Version -

Juniper>>Srx1400 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx210 >> Version -

Juniper>>Srx220 >> Version -

Juniper>>Srx240 >> Version -

Juniper>>Srx300 >> Version -

Juniper>>Srx320 >> Version -

Juniper>>Srx340 >> Version -

Juniper>>Srx3400 >> Version -

Juniper>>Srx345 >> Version -

Juniper>>Srx3600 >> Version -

Juniper>>Srx4100 >> Version -

Juniper>>Srx4200 >> Version -

Juniper>>Srx5400 >> Version -

Juniper>>Srx550 >> Version -

Juniper>>Srx5600 >> Version -

Juniper>>Srx5800 >> Version -

Juniper>>Srx650 >> Version -

Configuraton 0

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Srx100 >> Version -

Juniper>>Srx110 >> Version -

Juniper>>Srx1400 >> Version -

Juniper>>Srx1500 >> Version -

Juniper>>Srx210 >> Version -

Juniper>>Srx220 >> Version -

Juniper>>Srx240 >> Version -

Juniper>>Srx300 >> Version -

Juniper>>Srx320 >> Version -

Juniper>>Srx340 >> Version -

Juniper>>Srx3400 >> Version -

Juniper>>Srx345 >> Version -

Juniper>>Srx3600 >> Version -

Juniper>>Srx4100 >> Version -

Juniper>>Srx4200 >> Version -

Juniper>>Srx5400 >> Version -

Juniper>>Srx550 >> Version -

Juniper>>Srx5600 >> Version -

Juniper>>Srx5800 >> Version -

Juniper>>Srx650 >> Version -

Configuraton 0

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Ex_rps >> Version -

Juniper>>Ex2200 >> Version -

Juniper>>Ex2200-c >> Version -

Juniper>>Ex2300 >> Version -

Juniper>>Ex2300-c >> Version -

Juniper>>Ex3300 >> Version -

Juniper>>Ex3400 >> Version -

Juniper>>Ex4200 >> Version -

Juniper>>Ex4300 >> Version -

Juniper>>Ex4550 >> Version -

Juniper>>Ex4600 >> Version -

Juniper>>Ex9200 >> 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>>Ex2200\/vc >> Version -

    Juniper>>Ex3200 >> Version -

    Juniper>>Ex3300\/vc >> Version -

      Juniper>>Ex4200 >> Version -

      Juniper>>Ex4300 >> Version -

      Juniper>>Ex4550\/vc >> Version -

      Juniper>>Ex4600 >> Version -

      Juniper>>Ex6200 >> Version -

      Juniper>>Ex8200\/vc_\(xre\) >> Version -

        Juniper>>Qfx3500 >> Version -

        Juniper>>Qfx3600 >> Version -

        Juniper>>Qfx5100 >> Version -

        Configuraton 0

        Juniper>>Junos >> Version 15.1x49

        Juniper>>Junos >> Version 15.1x49

        Juniper>>Srx100 >> Version -

        Juniper>>Srx110 >> Version -

        Juniper>>Srx1400 >> Version -

        Juniper>>Srx1500 >> Version -

        Juniper>>Srx210 >> Version -

        Juniper>>Srx220 >> Version -

        Juniper>>Srx240 >> Version -

        Juniper>>Srx300 >> Version -

        Juniper>>Srx320 >> Version -

        Juniper>>Srx340 >> Version -

        Juniper>>Srx3400 >> Version -

        Juniper>>Srx345 >> Version -

        Juniper>>Srx3600 >> Version -

        Juniper>>Srx4100 >> Version -

        Juniper>>Srx4200 >> Version -

        Juniper>>Srx5400 >> Version -

        Juniper>>Srx550 >> Version -

        Juniper>>Srx5600 >> Version -

        Juniper>>Srx5800 >> Version -

        Juniper>>Srx650 >> Version -

        References

        http://www.securitytracker.com/id/1041314
        Tags : vdb-entry, x_refsource_SECTRACK
        https://kb.juniper.net/JSA10857
        Tags : x_refsource_CONFIRM
        http://www.securityfocus.com/bid/104718
        Tags : vdb-entry, x_refsource_BID