CVE-2018-7907 : Détail

CVE-2018-7907

5.5
/
Moyen
A01-Broken Access Control
0.07%V3
Local
2018-09-26
11h00 +00:00
2018-09-26
10h57 +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

Some Huawei products Agassi-L09 AGS-L09C100B257CUSTC100D001, AGS-L09C170B253CUSTC170D001, AGS-L09C199B251CUSTC199D001, AGS-L09C229B003CUSTC229D001, Agassi-W09 AGS-W09C100B257CUSTC100D001, AGS-W09C128B252CUSTC128D001, AGS-W09C170B252CUSTC170D001, AGS-W09C229B251CUSTC229D001, AGS-W09C331B003CUSTC331D001, AGS-W09C794B001CUSTC794D001, Baggio2-U01A BG2-U01C100B160CUSTC100D001, BG2-U01C170B160CUSTC170D001, BG2-U01C199B162CUSTC199D001, BG2-U01C209B160CUSTC209D001, BG2-U01C333B160CUSTC333D001, Bond-AL00C Bond-AL00CC00B201, Bond-AL10B Bond-AL10BC00B201, Bond-TL10B Bond-TL10BC01B201, Bond-TL10C Bond-TL10CC01B131, Haydn-L1JB HDN-L1JC137B068, Kobe-L09A KOB-L09C100B252CUSTC100D001, KOB-L09C209B002CUSTC209D001, KOB-L09C362B001CUSTC362D001, Kobe-L09AHN KOB-L09C233B226, Kobe-W09C KOB-W09C128B251CUSTC128D001, LelandP-L22C 8.0.0.101(C675CUSTC675D2), LelandP-L22D 8.0.0.101(C675CUSTC675D2), Rhone-AL00 Rhone-AL00C00B186, Selina-L02 Selina-L02C432B153, Stanford-L09S Stanford-L09SC432B183, Toronto-AL00 Toronto-AL00C00B223, Toronto-AL00A Toronto-AL00AC00B223, Toronto-TL10 Toronto-TL10C01B223 have a sensitive information leak vulnerability. An attacker can trick a user to install a malicious application to exploit this vulnerability. Due to insufficient verification of the input, successful exploitation can cause sensitive information leak.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 5.5 MEDIUM CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

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.3 AV:N/AC:M/Au:N/C:P/I:N/A:N [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

Huawei>>Agassi-l09_firmware >> Version ags-l09c100b257custc100d001

Huawei>>Agassi-l09_firmware >> Version ags-l09c170b253custc170d001

Huawei>>Agassi-l09_firmware >> Version ags-l09c199b251custc199d001

Huawei>>Agassi-l09_firmware >> Version ags-l09c229b003custc229d001

Huawei>>Agassi-l09 >> Version -

Configuraton 0

Huawei>>Agassi-w09_firmware >> Version ags-w09c100b257custc100d001

Huawei>>Agassi-w09_firmware >> Version ags-w09c128b252custc128d001

Huawei>>Agassi-w09_firmware >> Version ags-w09c170b252custc170d001

Huawei>>Agassi-w09_firmware >> Version ags-w09c229b251custc229d001

Huawei>>Agassi-w09_firmware >> Version ags-w09c331b003custc331d001

Huawei>>Agassi-w09_firmware >> Version ags-w09c794b001custc794d001

Huawei>>Agassi-w09 >> Version -

Configuraton 0

Huawei>>Baggio2-u01a_firmware >> Version bg2-u01c100b160custc100d001

Huawei>>Baggio2-u01a_firmware >> Version bg2-u01c170b160custc170d001

Huawei>>Baggio2-u01a_firmware >> Version bg2-u01c199b162custc199d001

Huawei>>Baggio2-u01a_firmware >> Version bg2-u01c209b160custc209d001

Huawei>>Baggio2-u01a_firmware >> Version bg2-u01c333b160custc333d001

Huawei>>Baggio2-u01a >> Version -

Configuraton 0

Huawei>>Bond-al00c_firmware >> Version bond-al00cc00b201

Huawei>>Bond-al00c >> Version -

Configuraton 0

Huawei>>Bond-al10b_firmware >> Version bond-al10bc00b201

Huawei>>Bond-al10b >> Version -

Configuraton 0

Huawei>>Bond-tl10b_firmware >> Version bond-tl10bc01b201

Huawei>>Bond-tl10b >> Version -

Configuraton 0

Huawei>>Bond-tl10c_firmware >> Version bond-tl10cc01b131

Huawei>>Bond-tl10c >> Version -

Configuraton 0

Huawei>>Haydn-l1jb_firmware >> Version hdn-l1jc137b068

Huawei>>Haydn-l1jb >> Version -

Configuraton 0

Huawei>>Kobe-l09a_firmware >> Version kob-l09c100b252custc100d001

Huawei>>Kobe-l09a_firmware >> Version kob-l09c209b002custc209d001

Huawei>>Kobe-l09a_firmware >> Version kob-l09c362b001custc362d001

Huawei>>Kobe-l09a >> Version -

Configuraton 0

Huawei>>Kobe-l09ahn_firmware >> Version kob-l09c233b226

Huawei>>Kobe-l09ahn >> Version -

Configuraton 0

Huawei>>Kobe-w09c_firmware >> Version kob-w09c128b251custc128d001

Huawei>>Kobe-w09c >> Version -

Configuraton 0

Huawei>>Lelandp-l22c_firmware >> Version 8.0.0.101_c675custc675d2

Huawei>>Lelandp-l22c >> Version -

Configuraton 0

Huawei>>Lelandp-l22d_firmware >> Version 8.0.0.101_c675custc675d2

Huawei>>Lelandp-l22d >> Version -

Configuraton 0

Huawei>>Rhone-al00_firmware >> Version rhone-al00c00b186

Huawei>>Rhone-al00 >> Version -

Configuraton 0

Huawei>>Selina-l02_firmware >> Version selina-l02c432b153

Huawei>>Selina-l02 >> Version -

Configuraton 0

Huawei>>Stanford-l09s_firmware >> Version stanford-l09sc432b183

Huawei>>Stanford-l09s >> Version -

Configuraton 0

Huawei>>Toronto-al00_firmware >> Version toronto-al00c00b223

Huawei>>Toronto-al00 >> Version -

Configuraton 0

Huawei>>Toronto-al00a_firmware >> Version toronto-al00ac00b223

Huawei>>Toronto-al00a >> Version -

Configuraton 0

Huawei>>Toronto-tl10_firmware >> Version toronto-tl10c01b223

Huawei>>Toronto-tl10 >> Version -

Références