CVE-2018-9085
Descrizioni CVE
Missing System x Flash Memory Write Protection Lock Bit
A write protection lock bit was left unset after boot on an older generation of Lenovo and IBM System x servers, potentially allowing an attacker with administrator access to modify the subset of flash memory containing Intel Server Platform Services (SPS) and the system Flash Descriptors.Soluzioni CVE
Informazioni CVE
Vulnerabilità correlate
| Nome della vulnerabilità | Source | |
|---|---|---|
| Incorrect Default Permissions During installation, installed file permissions are set to allow anyone to modify those files. |
Metriche
| Metriche | Punteggio | Gravità | CVSS Vettore | Source |
|---|---|---|---|---|
| V3.0 | 4.9 | MEDIUM |
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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 Vector This 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 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. High The attacker is authorized with (i.e. requires) privileges that provide significant (e.g. administrative) control over the vulnerable component that could affect component-wide settings and files. 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 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. 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. 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 |
nvd@nist.gov |
| V2 | 4 | AV:N/AC:L/Au:S/C:N/I:P/A:N | nvd@nist.gov |
EPSS
Punteggio EPSS
Percentile EPSS
Products Mentioned
Configuraton 0
Lenovo>>Flex_system_x240_m4_firmware >> Version To (excluding) a3e122b
Lenovo>>Flex_system_x240_m4 >> Version -
Configuraton 0
Lenovo>>Flex_system_x440_m4_firmware >> Version To (excluding) cge122b
Lenovo>>Flex_system_x440_m4 >> Version -
Configuraton 0
Lenovo>>System_x3750_m4_firmware >> Version To (excluding) a5e124b
Lenovo>>System_x3750_m4 >> Version -
Configuraton 0
Ibm>>Bladecenter_hs23_firmware >> Version To (excluding) tke160c
Ibm>>Bladecenter >> Version hs23
Configuraton 0
Ibm>>Bladecenter_hs23e_firmware >> Version To (excluding) ahe160c
Ibm>>Bladecenter >> Version hs23e
Configuraton 0
Ibm>>Flex_system_x220_m4_firmware >> Version To (excluding) kse158c
Ibm>>Flex_system_x220 >> Version -
Configuraton 0
Ibm>>Flex_system_x222_m4_firmware >> Version To (excluding) cce160c
Ibm>>Flex_system_x222_m4 >> Version -
Configuraton 0
Ibm>>Flex_system_x240_m4_firmware >> Version To (excluding) ahe160c
Ibm>>Flex_system_x240_m4 >> Version -
Configuraton 0
Ibm>>Flex_system_x280_x6_firmware >> Version To (excluding) n3e132w
Ibm>>Flex_system_x280_x6 >> Version -
Configuraton 0
Ibm>>Flex_system_x440_m4_firmware >> Version To (excluding) cne162d
Ibm>>Flex_system_x440_m4 >> Version -
Configuraton 0
Ibm>>Flex_system_x480_x6_firmware >> Version To (excluding) n3e132w
Ibm>>Flex_system_x480_x6 >> Version -
Configuraton 0
Ibm>>Flex_system_x880_x6_firmware >> Version To (excluding) n2e130e
Ibm>>Flex_system_x880_x6 >> Version -
Configuraton 0
Ibm>>Idataplex_dx360_m4_firmware >> Version To (excluding) fhe120d
Ibm>>Idataplex_dx360_m4_ >> Version -
Configuraton 0
Ibm>>Idataplex_dx360_m4_water_cooled_firmware >> Version To (excluding) fhe120d
Ibm>>Idataplex_dx360_m4_ >> Version -
Configuraton 0
Ibm>>System_x3100_m4_firmware >> Version To (excluding) jqe184c
Ibm>>System_x3100_m4 >> Version *
Configuraton 0
Ibm>>System_x3100_m5_firmware >> Version To (excluding) j9e134c
Ibm>>System_x3100_m5 >> Version *
Configuraton 0
Ibm>>System_x3250_m4_firmware >> Version To (excluding) jqe184c
Ibm>>System_x3250_m4 >> Version *
Configuraton 0
Ibm>>System_x3250_m5_firmware >> Version To (excluding) jue134c
Ibm>>System_x3250_m5 >> Version *
Configuraton 0
Ibm>>System_x3300_m4_firmware >> Version To (excluding) yae156c
Ibm>>System_x3300_m4 >> Version *
Configuraton 0
Ibm>>System_x3500_m4_firmware >> Version To (excluding) y5e158c
Ibm>>System_x3500_m4 >> Version *
Configuraton 0
Ibm>>System_x3530_m4_firmware >> Version To (excluding) bee164c
Ibm>>System_x3530_m4 >> Version *
Configuraton 0
Ibm>>System_x3550_m4_firmware >> Version To (excluding) d7e166d
Ibm>>System_x3550_m4 >> Version *
Configuraton 0
Ibm>>System_x3630_m4_firmware >> Version To (excluding) vve162c
Ibm>>System_x3630_m4 >> Version *
Configuraton 0
Ibm>>System_x3650_m4_firmware >> Version To (excluding) vve160c
Ibm>>System_x3650_m4 >> Version *
Configuraton 0
Ibm>>System_x3650_m4_bd_firmware >> Version To (excluding) vve160c
Ibm>>System_x3650_m4_bd >> Version *
Configuraton 0
Ibm>>System_x3650_m4_hd_firmware >> Version To (excluding) vve160c
Ibm>>System_x3650_m4_hd >> Version *
Configuraton 0
Ibm>>System_x3750_m4_firmware >> Version To (excluding) koe160c
Ibm>>System_x3750_m4 >> Version *
Configuraton 0
Ibm>>System_x3850_x6_firmware >> Version To (excluding) a8e128c
Ibm>>System_x3850_x6 >> Version *
Configuraton 0
Ibm>>System_x3950_x6_firmware >> Version To (excluding) bee164c
Ibm>>System_x3950_x6 >> Version *
