CVE-2017-17250 : Detail

CVE-2017-17250

6.5
/
Medium
Overflow
0.17%V4
Network
2018-03-09
16h00 +00:00
2018-03-09
15h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Huawei AR120-S V200R005C32; AR1200 V200R005C32; AR1200-S V200R005C32; AR150 V200R005C32; AR150-S V200R005C32; AR160 V200R005C32; AR200 V200R005C32; AR200-S V200R005C32; AR2200-S V200R005C32; AR3200 V200R005C32; V200R007C00; AR510 V200R005C32; NetEngine16EX V200R005C32; SRG1300 V200R005C32; SRG2300 V200R005C32; SRG3300 V200R005C32 have an out-of-bounds write vulnerability. When a user executes a query command after the device received an abnormal OSPF message, the software writes data past the end of the intended buffer due to the insufficient verification of the input data. An unauthenticated, remote attacker could exploit this vulnerability by sending abnormal OSPF messages to the device. A successful exploit could cause the system to crash.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-787 Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 6.5 MEDIUM CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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.

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.

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.

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.

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 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

 nvd@nist.gov
V2 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Huawei>>Ar120-s_firmware >> Version v200r005c32

Huawei>>Ar120-s >> Version -

Configuraton 0

Huawei>>Ar1200_firmware >> Version v200r005c32

Huawei>>Ar1200 >> Version -

Configuraton 0

Huawei>>Ar1200-s_firmware >> Version v200r005c32

Huawei>>Ar1200-s >> Version -

Configuraton 0

Huawei>>Ar150_firmware >> Version v200r005c32

Huawei>>Ar150 >> Version -

Configuraton 0

Huawei>>Ar160_firmware >> Version v200r005c32

Huawei>>Ar160 >> Version -

Configuraton 0

Huawei>>Ar200_firmware >> Version v200r005c32

Huawei>>Ar200 >> Version -

Configuraton 0

Huawei>>Ar200-s_firmware >> Version v200r005c32

Huawei>>Ar200-s >> Version -

Configuraton 0

Huawei>>Ar150-s_firmware >> Version v200r005c32

Huawei>>Ar150-s >> Version -

Configuraton 0

Huawei>>Ar2200-s_firmware >> Version v200r005c32

Huawei>>Ar2200-s >> Version -

Configuraton 0

Huawei>>Ar3200_firmware >> Version v200r005c32

Huawei>>Ar3200_firmware >> Version v200r007c00

Huawei>>Ar3200 >> Version -

Configuraton 0

Huawei>>Ar510_firmware >> Version v200r005c32

Huawei>>Ar510 >> Version -

Configuraton 0

Huawei>>Netengine16ex_firmware >> Version v200r005c32

Huawei>>Netengine16ex >> Version -

Configuraton 0

Huawei>>S12700_firmware >> Version v200r007c00

Huawei>>S12700_firmware >> Version v200r007c01

Huawei>>S12700_firmware >> Version v200r008c00

Huawei>>S12700 >> Version -

Configuraton 0

Huawei>>S2700_firmware >> Version v200r006c10

Huawei>>S2700_firmware >> Version v200r007c00

Huawei>>S2700_firmware >> Version v200r008c00

Huawei>>S2700 >> Version -

Configuraton 0

Huawei>>S5700_firmware >> Version v200r007c00

Huawei>>S5700_firmware >> Version v200r008c00

Huawei>>S5700 >> Version -

Configuraton 0

Huawei>>S6700_firmware >> Version v200r008c00

Huawei>>S6700 >> Version -

Configuraton 0

Huawei>>S7700_firmware >> Version v200r007c00

Huawei>>S7700_firmware >> Version v200r008c00

Huawei>>S7700 >> Version -

Configuraton 0

Huawei>>S9700_firmware >> Version v200r007c00

Huawei>>S9700_firmware >> Version v200r007c01

Huawei>>S9700_firmware >> Version v200r008c00

Huawei>>S9700 >> Version -

Configuraton 0

Huawei>>Srg1300_firmware >> Version v200r005c32

Huawei>>Srg1300 >> Version -

Configuraton 0

Huawei>>Srg2300_firmware >> Version v200r005c32

Huawei>>Srg2300 >> Version -

Configuraton 0

Huawei>>Srg3300_firmware >> Version v200r005c32

Huawei>>Srg3300 >> Version -

References

The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.