ID CVE-2018-0024
Summary 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.
References
Vulnerable Configurations
  • Juniper JUNOS 12.1X46
    cpe:2.3:o:juniper:junos:12.1x46
  • Juniper Junos 12.1x46 D10
    cpe:2.3:o:juniper:junos:12.1x46:d10
  • Juniper Junos 12.1x46 D15
    cpe:2.3:o:juniper:junos:12.1x46:d15
  • Juniper JUNOS 12.1X46-D20
    cpe:2.3:o:juniper:junos:12.1x46:d20
  • Juniper Junos 12.1x46 D25
    cpe:2.3:o:juniper:junos:12.1x46:d25
  • Juniper JunOS 12.1x46 D30
    cpe:2.3:o:juniper:junos:12.1x46:d30
  • Juniper JunOS 12.1x46 D35
    cpe:2.3:o:juniper:junos:12.1x46:d35
  • Juniper JunOS 12.1x46 D40
    cpe:2.3:o:juniper:junos:12.1x46:d40
  • Juniper SRX100
    cpe:2.3:h:juniper:srx100
  • Juniper SRX110
    cpe:2.3:h:juniper:srx110
  • Juniper SRX1400
    cpe:2.3:h:juniper:srx1400
  • cpe:2.3:h:juniper:srx1500
    cpe:2.3:h:juniper:srx1500
  • Juniper SRX210
    cpe:2.3:h:juniper:srx210
  • Juniper SRX220
    cpe:2.3:h:juniper:srx220
  • Juniper SRX240
    cpe:2.3:h:juniper:srx240
  • cpe:2.3:h:juniper:srx300
    cpe:2.3:h:juniper:srx300
  • cpe:2.3:h:juniper:srx320
    cpe:2.3:h:juniper:srx320
  • cpe:2.3:h:juniper:srx340
    cpe:2.3:h:juniper:srx340
  • Juniper SRX3400
    cpe:2.3:h:juniper:srx3400
  • cpe:2.3:h:juniper:srx345
    cpe:2.3:h:juniper:srx345
  • Juniper SRX3600
    cpe:2.3:h:juniper:srx3600
  • cpe:2.3:h:juniper:srx4100
    cpe:2.3:h:juniper:srx4100
  • cpe:2.3:h:juniper:srx4200
    cpe:2.3:h:juniper:srx4200
  • Juniper SRX5400
    cpe:2.3:h:juniper:srx5400
  • Juniper SRX550
    cpe:2.3:h:juniper:srx550
  • Juniper SRX5600
    cpe:2.3:h:juniper:srx5600
  • Juniper SRX5800
    cpe:2.3:h:juniper:srx5800
  • Juniper SRX650
    cpe:2.3:h:juniper:srx650
  • cpe:2.3:o:juniper:junos:12.3x48
    cpe:2.3:o:juniper:junos:12.3x48
  • Juniper JunOS 12.3x48 D10
    cpe:2.3:o:juniper:junos:12.3x48:d10
  • Juniper JunOS 12.3x48 D15
    cpe:2.3:o:juniper:junos:12.3x48:d15
  • Juniper SRX100
    cpe:2.3:h:juniper:srx100
  • Juniper SRX110
    cpe:2.3:h:juniper:srx110
  • Juniper SRX1400
    cpe:2.3:h:juniper:srx1400
  • cpe:2.3:h:juniper:srx1500
    cpe:2.3:h:juniper:srx1500
  • Juniper SRX210
    cpe:2.3:h:juniper:srx210
  • Juniper SRX220
    cpe:2.3:h:juniper:srx220
  • Juniper SRX240
    cpe:2.3:h:juniper:srx240
  • cpe:2.3:h:juniper:srx300
    cpe:2.3:h:juniper:srx300
  • cpe:2.3:h:juniper:srx320
    cpe:2.3:h:juniper:srx320
  • cpe:2.3:h:juniper:srx340
    cpe:2.3:h:juniper:srx340
  • Juniper SRX3400
    cpe:2.3:h:juniper:srx3400
  • cpe:2.3:h:juniper:srx345
    cpe:2.3:h:juniper:srx345
  • Juniper SRX3600
    cpe:2.3:h:juniper:srx3600
  • cpe:2.3:h:juniper:srx4100
    cpe:2.3:h:juniper:srx4100
  • cpe:2.3:h:juniper:srx4200
    cpe:2.3:h:juniper:srx4200
  • Juniper SRX5400
    cpe:2.3:h:juniper:srx5400
  • Juniper SRX550
    cpe:2.3:h:juniper:srx550
  • Juniper SRX5600
    cpe:2.3:h:juniper:srx5600
  • Juniper SRX5800
    cpe:2.3:h:juniper:srx5800
  • Juniper SRX650
    cpe:2.3:h:juniper:srx650
  • Juniper JUNOS 12.3
    cpe:2.3:o:juniper:junos:12.3
  • Juniper Junos 12.3 R1
    cpe:2.3:o:juniper:junos:12.3:r1
  • cpe:2.3:o:juniper:junos:12.3:r10
    cpe:2.3:o:juniper:junos:12.3:r10
  • Juniper Junos 12.3 R2
    cpe:2.3:o:juniper:junos:12.3:r2
  • Juniper Junos 12.3 R3
    cpe:2.3:o:juniper:junos:12.3:r3
  • Juniper Junos 12.3 R4
    cpe:2.3:o:juniper:junos:12.3:r4
  • Juniper Junos 12.3 R5
    cpe:2.3:o:juniper:junos:12.3:r5
  • Juniper Junos 12.3 R6
    cpe:2.3:o:juniper:junos:12.3:r6
  • Juniper JUNOS 12.3R7
    cpe:2.3:o:juniper:junos:12.3:r7
  • Juniper Junos 12.3 R8
    cpe:2.3:o:juniper:junos:12.3:r8
  • Juniper JunOS 12.3 R9
    cpe:2.3:o:juniper:junos:12.3:r9
  • cpe:2.3:h:juniper:ex2200
    cpe:2.3:h:juniper:ex2200
  • cpe:2.3:h:juniper:ex2200-c
    cpe:2.3:h:juniper:ex2200-c
  • cpe:2.3:h:juniper:ex2300
    cpe:2.3:h:juniper:ex2300
  • cpe:2.3:h:juniper:ex2300-c
    cpe:2.3:h:juniper:ex2300-c
  • cpe:2.3:h:juniper:ex3300
    cpe:2.3:h:juniper:ex3300
  • cpe:2.3:h:juniper:ex3400
    cpe:2.3:h:juniper:ex3400
  • cpe:2.3:h:juniper:ex4200
    cpe:2.3:h:juniper:ex4200
  • cpe:2.3:h:juniper:ex4300
    cpe:2.3:h:juniper:ex4300
  • cpe:2.3:h:juniper:ex4550
    cpe:2.3:h:juniper:ex4550
  • cpe:2.3:h:juniper:ex4600
    cpe:2.3:h:juniper:ex4600
  • cpe:2.3:h:juniper:ex9200
    cpe:2.3:h:juniper:ex9200
  • cpe:2.3:h:juniper:ex_rps
    cpe:2.3:h:juniper:ex_rps
  • Juniper JunOS 14.1x53
    cpe:2.3:o:juniper:junos:14.1x53
  • Juniper JunOS 14.1x53 D10
    cpe:2.3:o:juniper:junos:14.1x53:d10
  • Juniper JunOS 14.1x53 D15
    cpe:2.3:o:juniper:junos:14.1x53:d15
  • Juniper JunOS 14.1x53 D16
    cpe:2.3:o:juniper:junos:14.1x53:d16
  • Juniper JunOS 14.1x53 D25
    cpe:2.3:o:juniper:junos:14.1x53:d25
  • Juniper JunOS 14.1x53 D26
    cpe:2.3:o:juniper:junos:14.1x53:d26
  • Juniper Junos 14.1X53 D27
    cpe:2.3:o:juniper:junos:14.1x53:d27
  • cpe:2.3:h:juniper:ex2200%2fvc
    cpe:2.3:h:juniper:ex2200%2fvc
  • cpe:2.3:h:juniper:ex3200
    cpe:2.3:h:juniper:ex3200
  • cpe:2.3:h:juniper:ex3300%2fvc
    cpe:2.3:h:juniper:ex3300%2fvc
  • cpe:2.3:h:juniper:ex4200
    cpe:2.3:h:juniper:ex4200
  • cpe:2.3:h:juniper:ex4300
    cpe:2.3:h:juniper:ex4300
  • cpe:2.3:h:juniper:ex4550%2fvc
    cpe:2.3:h:juniper:ex4550%2fvc
  • cpe:2.3:h:juniper:ex4600
    cpe:2.3:h:juniper:ex4600
  • cpe:2.3:h:juniper:ex6200
    cpe:2.3:h:juniper:ex6200
  • cpe:2.3:h:juniper:ex8200%2fvc_%28xre%29
    cpe:2.3:h:juniper:ex8200%2fvc_%28xre%29
  • cpe:2.3:h:juniper:qfx3500
    cpe:2.3:h:juniper:qfx3500
  • cpe:2.3:h:juniper:qfx3600
    cpe:2.3:h:juniper:qfx3600
  • cpe:2.3:h:juniper:qfx5100
    cpe:2.3:h:juniper:qfx5100
  • cpe:2.3:o:juniper:junos:15.1x49
    cpe:2.3:o:juniper:junos:15.1x49
  • Juniper JunOS 15.1x49 D10
    cpe:2.3:o:juniper:junos:15.1x49:d10
  • Juniper SRX100
    cpe:2.3:h:juniper:srx100
  • Juniper SRX110
    cpe:2.3:h:juniper:srx110
  • Juniper SRX1400
    cpe:2.3:h:juniper:srx1400
  • cpe:2.3:h:juniper:srx1500
    cpe:2.3:h:juniper:srx1500
  • Juniper SRX210
    cpe:2.3:h:juniper:srx210
  • Juniper SRX220
    cpe:2.3:h:juniper:srx220
  • Juniper SRX240
    cpe:2.3:h:juniper:srx240
  • cpe:2.3:h:juniper:srx300
    cpe:2.3:h:juniper:srx300
  • cpe:2.3:h:juniper:srx320
    cpe:2.3:h:juniper:srx320
  • cpe:2.3:h:juniper:srx340
    cpe:2.3:h:juniper:srx340
  • Juniper SRX3400
    cpe:2.3:h:juniper:srx3400
  • cpe:2.3:h:juniper:srx345
    cpe:2.3:h:juniper:srx345
  • Juniper SRX3600
    cpe:2.3:h:juniper:srx3600
  • cpe:2.3:h:juniper:srx4100
    cpe:2.3:h:juniper:srx4100
  • cpe:2.3:h:juniper:srx4200
    cpe:2.3:h:juniper:srx4200
  • Juniper SRX5400
    cpe:2.3:h:juniper:srx5400
  • Juniper SRX550
    cpe:2.3:h:juniper:srx550
  • Juniper SRX5600
    cpe:2.3:h:juniper:srx5600
  • Juniper SRX5800
    cpe:2.3:h:juniper:srx5800
  • Juniper SRX650
    cpe:2.3:h:juniper:srx650
CVSS
Base: 7.2
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
nessus via4
NASL family Junos Local Security Checks
NASL id JUNIPER_JSA10857.NASL
description According to its self-reported version number, the remote Junos device is affected by a privilege escalation vulnerability.
last seen 2018-07-21
modified 2018-07-20
plugin id 111204
published 2018-07-20
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=111204
title Juniper Junos Privilege Escalation (JSA10857)
refmap via4
bid 104718
confirm https://kb.juniper.net/JSA10857
sectrack 1041314
Last major update 11-07-2018 - 14:29
Published 11-07-2018 - 14:29
Last modified 11-09-2018 - 09:15
Back to Top