CVE-2017-18293 : Detalle

CVE-2017-18293

7.8
/
Alto
0.04%V4
Local
2018-10-23
13h00 +00:00
2024-08-05
21h20 +00:00
Notificaciones para una CVE
Manténgase informado sobre cualquier cambio en una CVE específica.
Gestionar notificaciones

Descripciones CVE

When a particular GPIO is protected by blocking access to the corresponding GPIO resource registers, the protection can be bypassed using the corresponding banked GPIO registers instead in Snapdragon Mobile, Snapdragon Wear in version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 835, SDA660.

Informaciones CVE

Debilidades relacionadas

CWE-ID Nombre de la debilidad Source
CWE Other No informations.

Métricas

Métricas Puntuación Gravedad 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

nvd@nist.gov
V2 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C nvd@nist.gov

EPSS

EPSS es un modelo de puntuación que predice la probabilidad de que una vulnerabilidad sea explotada.

Puntuación EPSS

El modelo EPSS produce una puntuación de probabilidad entre 0 y 1 (0 y 100%). Cuanto mayor sea la puntuación, mayor será la probabilidad de que se explote una vulnerabilidad.

Percentil EPSS

El percentil se usa para clasificar las CVE según su puntuación EPSS. Por ejemplo, una CVE en el percentil 95 según su puntuación EPSS tiene más probabilidades de ser explotada que el 95% de otras CVE. Así, el percentil sirve para comparar la puntuación EPSS de una CVE con la de otras CVE.

Products Mentioned

Configuraton 0

Qualcomm>>Mdm9206_firmware >> Version -

Qualcomm>>Mdm9206 >> Version -

Configuraton 0

Qualcomm>>Mdm9607_firmware >> Version -

Qualcomm>>Mdm9607 >> Version -

Configuraton 0

Qualcomm>>Mdm9650_firmware >> Version -

Qualcomm>>Mdm9650 >> Version -

Configuraton 0

Qualcomm>>Sd_210_firmware >> Version -

Qualcomm>>Sd_210 >> Version -

Configuraton 0

Qualcomm>>Sd_212_firmware >> Version -

Qualcomm>>Sd_212 >> Version -

Configuraton 0

Qualcomm>>Sd_205_firmware >> Version -

Qualcomm>>Sd_205 >> Version -

Configuraton 0

Qualcomm>>Sd_425_firmware >> Version -

Qualcomm>>Sd_425 >> Version -

Configuraton 0

Qualcomm>>Sd_430_firmware >> Version -

Qualcomm>>Sd_430 >> Version -

Configuraton 0

Qualcomm>>Sd_450_firmware >> Version -

Qualcomm>>Sd_450 >> Version -

Configuraton 0

Qualcomm>>Sd_625_firmware >> Version -

Qualcomm>>Sd_625 >> Version -

Configuraton 0

Qualcomm>>Sd_650_firmware >> Version -

Qualcomm>>Sd_650 >> Version -

Configuraton 0

Qualcomm>>Sd_652_firmware >> Version -

Qualcomm>>Sd_652 >> Version -

Configuraton 0

Qualcomm>>Sd_835_firmware >> Version -

Qualcomm>>Sd_835 >> Version -

Configuraton 0

Qualcomm>>Sda660_firmware >> Version -

Qualcomm>>Sda660 >> Version -

Referencias

http://www.securitytracker.com/id/1041432
Tags : vdb-entry, x_refsource_SECTRACK