CVE-2018-8340
Alerte pour un CVE
Descriptions
Informations
Faiblesses connexes
| Nom de la faiblesse | Source | |
|---|---|---|
| No informations. |
Metrics
| Metric | Score | Sévérité | CVSS Vecteur | Source |
|---|---|---|---|---|
| V3.0 | 6.5 | MEDIUM |
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
More informations
Base: Exploitabilty MetricsThe Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack VectorThis metric reflects the context by which vulnerability exploitation is possible. Network A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers). Attack ComplexityThis 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 RequiredThis 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 InteractionThis 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 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. ScopeFormally, 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 ImpactThis 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 ImpactThis 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 ImpactThis 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 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 |
[email protected] |
| V2 | 4 | AV:N/AC:L/Au:S/C:P/I:N/A:N | [email protected] |
EPSS
EPSS Score
EPSS Percentile
Products Mentioned
Configuraton 0
Microsoft>>Windows_server_2012 >> Version r2
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
- Microsoft>>Windows_server_2012 >> Version r2 (Open CPE detail)
Microsoft>>Windows_server_2016 >> Version -
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
- Microsoft>>Windows_server_2016 >> Version - (Open CPE detail)
Microsoft>>Windows_server_2016 >> Version 1709
- Microsoft>>Windows_server_2016 >> Version 1709 (Open CPE detail)
Microsoft>>Windows_server_2016 >> Version 1803
- Microsoft>>Windows_server_2016 >> Version 1803 (Open CPE detail)
References
Tags : x_refsource_CONFIRM
