CVE-2016-6369 : Détail

CVE-2016-6369

7.8
/
Haute
A01-Broken Access Control
0.04%V3
Local
2016-08-25
19h00 +00:00
2016-11-25
19h57 +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

Cisco AnyConnect Secure Mobility Client before 4.2.05015 and 4.3.x before 4.3.02039 mishandles pathnames, which allows local users to gain privileges via a crafted INF file, aka Bug ID CSCuz92464.

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 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C [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

Products Mentioned

Configuraton 0

Cisco>>Anyconnect_secure_mobility_client >> Version 2.0.0343

    Cisco>>Anyconnect_secure_mobility_client >> Version 2.1.0148

      Cisco>>Anyconnect_secure_mobility_client >> Version 2.2.0133

        Cisco>>Anyconnect_secure_mobility_client >> Version 2.2.0136

          Cisco>>Anyconnect_secure_mobility_client >> Version 2.2.0140

            Cisco>>Anyconnect_secure_mobility_client >> Version 2.3.0185

              Cisco>>Anyconnect_secure_mobility_client >> Version 2.3.0254

                Cisco>>Anyconnect_secure_mobility_client >> Version 2.3.1003

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.3.2016

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.4.0202

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.4.1012

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.0217

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2006

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2010

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2011

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2014

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2017

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2018

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.2019

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.3041

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.3046

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.3051

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.3054

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5.3055

                  Cisco>>Anyconnect_secure_mobility_client >> Version 2.5_base

                    Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.0

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.0629

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.1047

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.2052

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.3050

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.3054

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.4235

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.5075

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.5080

                      Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.09231

                        Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.09266

                          Cisco>>Anyconnect_secure_mobility_client >> Version 3.0.09353

                            Cisco>>Anyconnect_secure_mobility_client >> Version 3.1\(60\)

                            Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.0

                            Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.02043

                              Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.05182

                                Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.05187

                                  Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.06073

                                    Cisco>>Anyconnect_secure_mobility_client >> Version 3.1.07021

                                      Cisco>>Anyconnect_secure_mobility_client >> Version 4.0\(48\)

                                        Cisco>>Anyconnect_secure_mobility_client >> Version 4.0\(64\)

                                          Cisco>>Anyconnect_secure_mobility_client >> Version 4.0\(2049\)

                                          Cisco>>Anyconnect_secure_mobility_client >> Version 4.0.0

                                            Cisco>>Anyconnect_secure_mobility_client >> Version 4.0.00048

                                              Cisco>>Anyconnect_secure_mobility_client >> Version 4.0.00051

                                                Cisco>>Anyconnect_secure_mobility_client >> Version 4.1\(8\)

                                                  Cisco>>Anyconnect_secure_mobility_client >> Version 4.1.0

                                                    Cisco>>Anyconnect_secure_mobility_client >> Version 4.2.0

                                                    Cisco>>Anyconnect_secure_mobility_client >> Version 4.2.04039

                                                    Cisco>>Anyconnect_secure_mobility_client >> Version 4.3.0

                                                    Cisco>>Anyconnect_secure_mobility_client >> Version 4.3.00748

                                                    Cisco>>Anyconnect_secure_mobility_client >> Version 4.3.01095

                                                    Références

                                                    http://www.securitytracker.com/id/1036697
                                                    Tags : vdb-entry, x_refsource_SECTRACK
                                                    http://www.securityfocus.com/bid/92625
                                                    Tags : vdb-entry, x_refsource_BID