CVE-2017-8164
19h00 +00:00
CVE の説明
CVE の情報
関連する弱点
| 弱点名 | 出典 | |
|---|---|---|
| Improper Input Validation The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
メトリクス
| メトリクス | スコア | 深刻度 | CVSS ベクター | 出典 |
|---|---|---|---|---|
| V3.0 | 3.3 | LOW |
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
詳細情報
Base: Exploitabilty MetricsThe 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 MetricsAn 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 MetricsThe 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. None There is no loss of confidentiality within the impacted component. 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. Low There is reduced performance or interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component. Temporal MetricsThe 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 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P | nvd@nist.gov |
EPSS
EPSSスコア
EPSSパーセンタイル
関連製品
構成 0
Huawei>>Eva-al10_firmware >> Version eva-al10c00b198
Huawei>>Eva-al10 >> Version -
構成 0
Huawei>>Eva-cl00_firmware >> Version eva-cl00c92b198
Huawei>>Eva-cl00 >> Version -
構成 0
Huawei>>Eva-dl00_firmware >> Version eva-dl00c17b198
Huawei>>Eva-dl00 >> Version -
構成 0
Huawei>>Eva-l09_firmware >> Version eva-l09c02b143
Huawei>>Eva-l09_firmware >> Version eva-l09c09b150
Huawei>>Eva-l09_firmware >> Version eva-l09c22b140
Huawei>>Eva-l09_firmware >> Version eva-l09c25b133
Huawei>>Eva-l09_firmware >> Version eva-l09c33b191
Huawei>>Eva-l09_firmware >> Version eva-l09c34b142
Huawei>>Eva-l09_firmware >> Version eva-l09c40b196
Huawei>>Eva-l09_firmware >> Version eva-l09c55b190
Huawei>>Eva-l09_firmware >> Version eva-l09c109b196
Huawei>>Eva-l09_firmware >> Version eva-l09c113b150
Huawei>>Eva-l09_firmware >> Version eva-l09c150b192
Huawei>>Eva-l09_firmware >> Version eva-l09c178b161
Huawei>>Eva-l09_firmware >> Version eva-l09c185b180
Huawei>>Eva-l09_firmware >> Version eva-l09c432b210
Huawei>>Eva-l09_firmware >> Version eva-l09c440b138
Huawei>>Eva-l09_firmware >> Version eva-l09c464b150
Huawei>>Eva-l09_firmware >> Version eva-l09c530b127
Huawei>>Eva-l09_firmware >> Version eva-l09c576b150
Huawei>>Eva-l09_firmware >> Version eva-l09c635b221
Huawei>>Eva-l09_firmware >> Version eva-l09c636b193
Huawei>>Eva-l09_firmware >> Version eva-l09c675b130
Huawei>>Eva-l09_firmware >> Version eva-l09c688b143
Huawei>>Eva-l09_firmware >> Version eva-l09c703b160
Huawei>>Eva-l09_firmware >> Version eva-l09c706b145
Huawei>>Eva-l09_firmware >> Version eva-l09gbrc555b171
Huawei>>Eva-l09_firmware >> Version eva-l09irlc368b160
Huawei>>Eva-l09 >> Version -
構成 0
Huawei>>Eva-l19_firmware >> Version eva-l19c10b190
Huawei>>Eva-l19_firmware >> Version eva-l19c20b160
Huawei>>Eva-l19_firmware >> Version eva-l19c185b220
Huawei>>Eva-l19_firmware >> Version eva-l19c432b210
Huawei>>Eva-l19_firmware >> Version eva-l19c636b190
Huawei>>Eva-l19 >> Version -
構成 0
Huawei>>Eva-l29_firmware >> Version eva-l29c20b160
Huawei>>Eva-l29_firmware >> Version eva-l29c636b191
Huawei>>Eva-l29 >> Version -
構成 0
Huawei>>Eva-tl00_firmware >> Version eva-tl00c01b198
Huawei>>Eva-tl00 >> Version -
構成 0
Huawei>>Vie-l09_firmware >> Version vie-l09c02b131
Huawei>>Vie-l09_firmware >> Version vie-l09c25b120
Huawei>>Vie-l09_firmware >> Version vie-l09c40b181
Huawei>>Vie-l09_firmware >> Version vie-l09c55b170
Huawei>>Vie-l09_firmware >> Version vie-l09c109b181
Huawei>>Vie-l09_firmware >> Version vie-l09c113b170
Huawei>>Vie-l09_firmware >> Version vie-l09c150b170
Huawei>>Vie-l09_firmware >> Version vie-l09c432b181
Huawei>>Vie-l09_firmware >> Version vie-l09c605b131
Huawei>>Vie-l09_firmware >> Version vie-l09itac555b130
Huawei>>Vie-l09 >> Version -
構成 0
Huawei>>Vie-l29_firmware >> Version vie-l29c10b170
Huawei>>Vie-l29_firmware >> Version vie-l29c185b181
Huawei>>Vie-l29_firmware >> Version vie-l29c605b131
Huawei>>Vie-l29_firmware >> Version vie-l29c636b202
Huawei>>Vie-l29 >> Version -
参考資料
Tags : x_refsource_CONFIRM
