CVE-2017-17141 : Detail

CVE-2017-17141

3.7
/
Low
0.11%V3
Network
2018-03-05
19h00 +00:00
2024-09-17
03h23 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Huawei S12700 V200R005C00; V200R006C00; V200R007C00; V200R007C01; V200R007C20; V200R008C00; V200R009C00;S1700 V200R006C10; V200R009C00;S2700 V100R006C03; V200R003C00; V200R005C00; V200R006C00; V200R006C10; V200R007C00; V200R007C00B050; V200R007C00SPC009T; V200R007C00SPC019T; V200R008C00; V200R009C00;S3700 V100R006C03;S5700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R003C02; V200R005C00; V200R005C01; V200R005C02; V200R005C03; V200R006C00; V200R007C00; V200R008C00; V200R009C00;S6700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R005C01; V200R005C02; V200R008C00; V200R009C00;S7700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R006C00; V200R006C01; V200R007C00; V200R007C01; V200R008C00; V200R008C06; V200R009C00;S9700 V200R001C00; V200R001C01; V200R002C00; V200R003C00; V200R005C00; V200R006C00; V200R007C00; V200R007C01; V200R008C00; V200R009C00 have a memory leak vulnerability. In some specific conditions, if attackers send specific malformed MPLS Service PING messages to the affected products, products do not release the memory when handling the packets. So successful exploit will result in memory leak of the affected products.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-772 Missing Release of Resource after Effective Lifetime
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Metrics

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

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.

High

A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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.

None

The vulnerable system can be exploited without interaction from any user.

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.

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

 [email protected]
V2 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P [email protected]

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>>S12700_firmware >> Version v200r005c00

Huawei>>S12700_firmware >> Version v200r006c00

Huawei>>S12700_firmware >> Version v200r007c00

Huawei>>S12700_firmware >> Version v200r007c01

Huawei>>S12700_firmware >> Version v200r007c20

Huawei>>S12700_firmware >> Version v200r008c00

Huawei>>S12700_firmware >> Version v200r009c00

Huawei>>S12700 >> Version -

Configuraton 0

Huawei>>S1700_firmware >> Version v200r006c10

Huawei>>S1700_firmware >> Version v200r009c00

Huawei>>S1700 >> Version -

Configuraton 0

Huawei>>S2700_firmware >> Version v100r006c03

Huawei>>S2700_firmware >> Version v200r003c00

Huawei>>S2700_firmware >> Version v200r005c00

Huawei>>S2700_firmware >> Version v200r006c00

Huawei>>S2700_firmware >> Version v200r006c10

Huawei>>S2700_firmware >> Version v200r007c00

Huawei>>S2700_firmware >> Version v200r007c00b050

Huawei>>S2700_firmware >> Version v200r007c00spc009t

Huawei>>S2700_firmware >> Version v200r007c00spc019t

Huawei>>S2700_firmware >> Version v200r008c00

Huawei>>S2700_firmware >> Version v200r009c00

Huawei>>S2700 >> Version -

Configuraton 0

Huawei>>S3700_firmware >> Version v100r006c03

Huawei>>S3700 >> Version -

Configuraton 0

Huawei>>S5700_firmware >> Version v200r001c00

Huawei>>S5700_firmware >> Version v200r001c01

Huawei>>S5700_firmware >> Version v200r002c00

Huawei>>S5700_firmware >> Version v200r003c00

Huawei>>S5700_firmware >> Version v200r003c02

Huawei>>S5700_firmware >> Version v200r005c00

Huawei>>S5700_firmware >> Version v200r005c01

Huawei>>S5700_firmware >> Version v200r005c02

Huawei>>S5700_firmware >> Version v200r005c03

Huawei>>S5700_firmware >> Version v200r006c00

Huawei>>S5700_firmware >> Version v200r007c00

Huawei>>S5700_firmware >> Version v200r008c00

Huawei>>S5700_firmware >> Version v200r009c00

Huawei>>S5700 >> Version -

Configuraton 0

Huawei>>S6700_firmware >> Version v200r001c00

Huawei>>S6700_firmware >> Version v200r001c01

Huawei>>S6700_firmware >> Version v200r002c00

Huawei>>S6700_firmware >> Version v200r003c00

Huawei>>S6700_firmware >> Version v200r005c00

Huawei>>S6700_firmware >> Version v200r005c01

Huawei>>S6700_firmware >> Version v200r005c02

Huawei>>S6700_firmware >> Version v200r008c00

Huawei>>S6700_firmware >> Version v200r009c00

Huawei>>S6700 >> Version -

Configuraton 0

Huawei>>S7700_firmware >> Version v200r001c00

Huawei>>S7700_firmware >> Version v200r001c01

Huawei>>S7700_firmware >> Version v200r002c00

Huawei>>S7700_firmware >> Version v200r003c00

Huawei>>S7700_firmware >> Version v200r005c00

Huawei>>S7700_firmware >> Version v200r006c00

Huawei>>S7700_firmware >> Version v200r006c01

Huawei>>S7700_firmware >> Version v200r007c00

Huawei>>S7700_firmware >> Version v200r007c01

Huawei>>S7700_firmware >> Version v200r008c00

Huawei>>S7700_firmware >> Version v200r008c06

Huawei>>S7700_firmware >> Version v200r009c00

Huawei>>S7700 >> Version -

Configuraton 0

Huawei>>S9700_firmware >> Version v200r001c00

Huawei>>S9700_firmware >> Version v200r001c01

Huawei>>S9700_firmware >> Version v200r002c00

Huawei>>S9700_firmware >> Version v200r003c00

Huawei>>S9700_firmware >> Version v200r005c00

Huawei>>S9700_firmware >> Version v200r006c00

Huawei>>S9700_firmware >> Version v200r007c00

Huawei>>S9700_firmware >> Version v200r007c01

Huawei>>S9700_firmware >> Version v200r008c00

Huawei>>S9700_firmware >> Version v200r009c00

Huawei>>S9700 >> Version -

References