CVE-2018-21156
17h14 +00:00
Deskripsi CVE
Informasi CVE
Kelemahan Terkait
| Nama Kelemahan | Sumber | |
|---|---|---|
| Buffer Copy without Checking Size of Input The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Metrik
| Metrik | Skor | Tingkat keparahan | CVSS Vektor | Sumber |
|---|---|---|---|---|
| V3.1 | 7.2 | HIGH |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Informasi lebih lanjut
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 The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more 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 when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. High The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files. User Interaction This metric captures the requirement for a human 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 MetricsThe Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact MetricsThe Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. 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 a 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 a 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 MetricsThe Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental MetricsThese metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability. |
nvd@nist.gov |
| V3.0 | 6.8 | MEDIUM |
CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:U/UI:N
Informasi lebih lanjut
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. Adjacent A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router). 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. 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 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 |
|
| V3.0 | 6.8 | MEDIUM |
CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Informasi lebih lanjut
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. Adjacent A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router). 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. 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 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 |
cve@mitre.org |
| V2 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P | nvd@nist.gov |
EPSS
Skor EPSS
Persentil EPSS
Produk yang Disebutkan
Konfigurasi 0
Netgear>>D6220_firmware >> Version Hingga (tidak termasuk) 1.0.0.38
Netgear>>D6220 >> Version -
Konfigurasi 0
Netgear>>D6400_firmware >> Version Hingga (tidak termasuk) 1.0.0.74
Netgear>>D6400 >> Version -
Konfigurasi 0
Netgear>>D7000_firmware >> Version Hingga (tidak termasuk) 1.0.0.74
Netgear>>D7000 >> Version v2
Konfigurasi 0
Netgear>>D8500_firmware >> Version Hingga (tidak termasuk) 1.0.3.39
Netgear>>D8500 >> Version -
Konfigurasi 0
Netgear>>Dgn2200_firmware >> Version Hingga (tidak termasuk) 1.0.0.102
Netgear>>Dgn2200 >> Version v4
Konfigurasi 0
Netgear>>Dgn2200b_firmware >> Version Hingga (tidak termasuk) 1.0.0.102
Netgear>>Dgn2200b >> Version v4
Konfigurasi 0
Netgear>>Ex3700_firmware >> Version Hingga (tidak termasuk) 1.0.0.70
Netgear>>Ex3700 >> Version -
Konfigurasi 0
Netgear>>Ex3800_firmware >> Version Hingga (tidak termasuk) 1.0.0.70
Netgear>>Ex3800 >> Version -
Konfigurasi 0
Netgear>>Ex6000_firmware >> Version Hingga (tidak termasuk) 1.0.0.30
Netgear>>Ex6000 >> Version -
Konfigurasi 0
Netgear>>Ex6100_firmware >> Version Hingga (tidak termasuk) 1.0.2.22
Netgear>>Ex6100 >> Version -
Konfigurasi 0
Netgear>>Ex6120_firmware >> Version Hingga (tidak termasuk) 1.0.0.40
Netgear>>Ex6120 >> Version -
Konfigurasi 0
Netgear>>Ex6130_firmware >> Version Hingga (tidak termasuk) 1.0.0.22
Netgear>>Ex6130 >> Version -
Konfigurasi 0
Netgear>>Ex6150_firmware >> Version Hingga (tidak termasuk) 1.0.0.38
Netgear>>Ex6150 >> Version -
Konfigurasi 0
Netgear>>Ex6200_firmware >> Version Hingga (tidak termasuk) 1.0.3.86
Netgear>>Ex6200 >> Version -
Konfigurasi 0
Netgear>>Ex7000_firmware >> Version Hingga (tidak termasuk) 1.0.0.64
Netgear>>Ex7000 >> Version -
Konfigurasi 0
Netgear>>R6250_firmware >> Version Hingga (tidak termasuk) 1.0.4.20
Netgear>>R6250 >> Version -
Konfigurasi 0
Netgear>>R6300_firmware >> Version Hingga (tidak termasuk) 1.0.4.22
Netgear>>R6300 >> Version v2
Konfigurasi 0
Netgear>>R6400_firmware >> Version Hingga (tidak termasuk) 1.0.1.32
Netgear>>R6400 >> Version -
Konfigurasi 0
Netgear>>R6400_firmware >> Version Hingga (tidak termasuk) 1.0.2.52
Netgear>>R6400 >> Version v2
Konfigurasi 0
Netgear>>R6700_firmware >> Version Hingga (tidak termasuk) 1.0.1.44
Netgear>>R6700 >> Version -
Konfigurasi 0
Netgear>>R6900_firmware >> Version Hingga (tidak termasuk) 1.0.1.44
Netgear>>R6900 >> Version -
Konfigurasi 0
Netgear>>R6900p_firmware >> Version Hingga (tidak termasuk) 1.3.0.18
Netgear>>R6900p >> Version -
Konfigurasi 0
Netgear>>R7000_firmware >> Version Hingga (tidak termasuk) 1.0.9.28
Netgear>>R7000 >> Version -
Konfigurasi 0
Netgear>>R7000p_firmware >> Version Hingga (tidak termasuk) 1.3.0.18
Netgear>>R7000p >> Version -
Konfigurasi 0
Netgear>>R7300dst_firmware >> Version Hingga (tidak termasuk) 1.0.0.62
Netgear>>R7300dst >> Version -
Konfigurasi 0
Netgear>>R7900_firmware >> Version Hingga (tidak termasuk) 1.0.2.10
Netgear>>R7900 >> Version -
Konfigurasi 0
Netgear>>R7900p_firmware >> Version Hingga (tidak termasuk) 1.3.0.10
Netgear>>R7900p >> Version -
Konfigurasi 0
Netgear>>R8000_firmware >> Version Hingga (tidak termasuk) 1.0.4.12
Netgear>>R8000 >> Version -
Konfigurasi 0
Netgear>>R8000p_firmware >> Version Hingga (tidak termasuk) 1.3.0.10
Netgear>>R8000p >> Version -
Konfigurasi 0
Netgear>>R8300_firmware >> Version Hingga (tidak termasuk) 1.0.2.116
Netgear>>R8300 >> Version -
Konfigurasi 0
Netgear>>R8500_firmware >> Version Hingga (tidak termasuk) 1.0.2.116
Netgear>>R8500 >> Version -
Konfigurasi 0
Netgear>>Wn2500rp_firmware >> Version Hingga (tidak termasuk) 1.0.1.52
Netgear>>Wn2500rp >> Version v2
Konfigurasi 0
Netgear>>Wndr3400_firmware >> Version Hingga (tidak termasuk) 1.0.1.18
Netgear>>Wndr3400 >> Version v3
Konfigurasi 0
Netgear>>Wnr3500l_firmware >> Version Hingga (tidak termasuk) 1.2.0.46
Netgear>>Wnr3500l >> Version v2
