7.5
HIGH
CVE-2017-8147
Huawei OSPF MaxAge LSA Remote Denial of Service
Description

AC6005 V200R006C10SPC200,AC6605 V200R006C10SPC200,AR1200 with software V200R005C10CP0582T, V200R005C10HP0581T, V200R005C20SPC026T,AR200 with software V200R005C20SPC026T,AR3200 V200R005C20SPC026T,CloudEngine 12800 with software V100R003C00, V100R005C00, V100R005C10, V100R006C00, V200R001C00,CloudEngine 5800 with software V100R003C00, V100R005C00, V100R005C10, V100R006C00, V200R001C00,CloudEngine 6800 with software V100R003C00, V100R005C00, V100R005C10, V100R006C00, V200R001C00,CloudEngine 7800 with software V100R003C00, V100R005C00, V100R005C10, V100R006C00, V200R001C00,CloudEngine 8800 with software V100R006C00, V200R001C00,E600 V200R008C00,S12700 with software V200R005C00, V200R006C00, V200R007C00, V200R008C00,S1700 with software V100R006C00, V100R007C00, V200R006C00,S2300 with software V100R005C00, V100R006C00, V100R006C03, V100R006C05, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R005C01, V200R005C02, V200R005C03, V200R006C00, V200R007C00, V200R008C00,S2700 with software V100R005C00, V100R006C00, V100R006C03, V100R006C05, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R005C01, V200R005C02, V200R005C03, V200R006C00, V200R007C00, V200R008C00,S5300 with software V100R005C00, V100R006C00, V100R006C01, V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R006C00, V200R007C00, V200R008C00,S5700 with software V100R005C00, V100R006C00, V100R006C01, V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R006C00, V200R007C00, V200R008C00,S6300 with software V100R006C00, V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R008C00,S6700 with software V100R006C00, V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R003C02, V200R003C10, V200R005C00, V200R006C00, V200R007C00, V200R008C00,S7700 with software V100R003C00, V100R006C00, V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00,S9300 with software V100R001C00, V100R002C00, V100R003C00, V100R006C00, V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R008C10,S9700 with software V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00,Secospace USG6600 V500R001C00SPC050 have a MaxAge LSA vulnerability due to improper OSPF implementation. When the device receives special LSA packets, the LS (Link Status) age would be set to MaxAge, 3600 seconds. An attacker can exploit this vulnerability to poison the route table and launch a DoS attack.

INFO

Published Date :

Nov. 22, 2017, 7:29 p.m.

Last Modified :

Dec. 8, 2017, 2:47 p.m.

Source :

[email protected]

Remotely Exploitable :

Yes !

Impact Score :

3.6

Exploitability Score :

3.9
Affected Products

The following products are affected by CVE-2017-8147 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Huawei cloudengine_12800_firmware
2 Huawei cloudengine_5800_firmware
3 Huawei cloudengine_6800_firmware
4 Huawei cloudengine_7800_firmware
5 Huawei secospace_usg6600_firmware
6 Huawei ac6005_firmware
7 Huawei ac6605_firmware
8 Huawei ar1200_firmware
9 Huawei ar200_firmware
10 Huawei ar3200_firmware
11 Huawei cloudengine_8800_firmware
12 Huawei e600_firmware
13 Huawei s12700_firmware
14 Huawei s1700_firmware
15 Huawei s2300_firmware
16 Huawei s2700_firmware
17 Huawei s5300_firmware
18 Huawei s5700_firmware
19 Huawei s6300_firmware
20 Huawei s6700_firmware
21 Huawei s7700_firmware
22 Huawei s9300_firmware
23 Huawei s9700_firmware
: Total Affected Vendor : 1 | Products : 23
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2017-8147.

URL Resource
http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20170720-01-ospf-en Issue Tracking Mitigation Vendor Advisory

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2017-8147 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2017-8147 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • Initial Analysis by [email protected]

    Dec. 08, 2017

    Action Type Old Value New Value
    Added CVSS V2 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
    Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    Changed Reference Type http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20170720-01-ospf-en No Types Assigned http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20170720-01-ospf-en Issue Tracking, Mitigation, Vendor Advisory
    Added CWE CWE-20
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ac6005_firmware:v200r006c10spc200:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ac6005:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ac6605_firmware:v200r006c10spc200:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ac6605:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar1200_firmware:v200r005c10cp0582t:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r005c10hp0581t:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r005c20spc026t:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar200_firmware:v200r005c20spc026t:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar3200_firmware:v200r005c20spc026t:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:cloudengine_12800_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_12800_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_12800_firmware:v100r005c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_12800_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_12800_firmware:v200r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:cloudengine_12800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:cloudengine_5800_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_5800_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_5800_firmware:v100r005c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_5800_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_5800_firmware:v200r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:cloudengine_5800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:cloudengine_6800_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_6800_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_6800_firmware:v100r005c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_6800_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_6800_firmware:v200r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:cloudengine_6800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:cloudengine_7800_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_7800_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_7800_firmware:v100r005c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_7800_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_7800_firmware:v200r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:cloudengine_7800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:cloudengine_8800_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:cloudengine_8800_firmware:v200r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:cloudengine_8800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:e600_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:e600:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s12700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s12700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s12700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s12700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s12700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s1700_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s1700_firmware:v100r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s1700_firmware:v200r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s1700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s2300_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v100r006c03:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v100r006c05:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r005c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r005c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r005c03:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2300_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s2300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s2700_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v100r006c03:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v100r006c05:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r005c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r005c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r005c03:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s2700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s2700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s5300_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v100r006c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5300_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s5300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s5700_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v100r006c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s5700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s5700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s6300_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6300_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s6300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s6700_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r003c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s6700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s7700_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s7700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s7700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s9300_firmware:v100r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v100r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v100r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v100r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r008c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9300_firmware:v200r008c10:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s9300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:s9700_firmware:v200r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:s9700_firmware:v200r008c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:s9700:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2017-8147 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2017-8147 weaknesses.

CAPEC-3: Using Leading 'Ghost' Character Sequences to Bypass Input Filters Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-7: Blind SQL Injection Blind SQL Injection CAPEC-8: Buffer Overflow in an API Call Buffer Overflow in an API Call CAPEC-9: Buffer Overflow in Local Command-Line Utilities Buffer Overflow in Local Command-Line Utilities CAPEC-10: Buffer Overflow via Environment Variables Buffer Overflow via Environment Variables CAPEC-13: Subverting Environment Variable Values Subverting Environment Variable Values CAPEC-14: Client-side Injection-induced Buffer Overflow Client-side Injection-induced Buffer Overflow CAPEC-22: Exploiting Trust in Client Exploiting Trust in Client CAPEC-23: File Content Injection File Content Injection CAPEC-24: Filter Failure through Buffer Overflow Filter Failure through Buffer Overflow CAPEC-28: Fuzzing Fuzzing CAPEC-31: Accessing/Intercepting/Modifying HTTP Cookies Accessing/Intercepting/Modifying HTTP Cookies CAPEC-42: MIME Conversion MIME Conversion CAPEC-43: Exploiting Multiple Input Interpretation Layers Exploiting Multiple Input Interpretation Layers CAPEC-45: Buffer Overflow via Symbolic Links Buffer Overflow via Symbolic Links CAPEC-46: Overflow Variables and Tags Overflow Variables and Tags CAPEC-47: Buffer Overflow via Parameter Expansion Buffer Overflow via Parameter Expansion CAPEC-52: Embedding NULL Bytes Embedding NULL Bytes CAPEC-53: Postfix, Null Terminate, and Backslash Postfix, Null Terminate, and Backslash CAPEC-63: Cross-Site Scripting (XSS) Cross-Site Scripting (XSS) CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic Using Slashes and URL Encoding Combined to Bypass Validation Logic CAPEC-67: String Format Overflow in syslog() String Format Overflow in syslog() CAPEC-71: Using Unicode Encoding to Bypass Validation Logic Using Unicode Encoding to Bypass Validation Logic CAPEC-72: URL Encoding URL Encoding CAPEC-73: User-Controlled Filename User-Controlled Filename CAPEC-78: Using Escaped Slashes in Alternate Encoding Using Escaped Slashes in Alternate Encoding CAPEC-79: Using Slashes in Alternate Encoding Using Slashes in Alternate Encoding CAPEC-80: Using UTF-8 Encoding to Bypass Validation Logic Using UTF-8 Encoding to Bypass Validation Logic CAPEC-81: Web Server Logs Tampering Web Server Logs Tampering CAPEC-83: XPath Injection XPath Injection CAPEC-85: AJAX Footprinting AJAX Footprinting CAPEC-88: OS Command Injection OS Command Injection CAPEC-101: Server Side Include (SSI) Injection Server Side Include (SSI) Injection CAPEC-104: Cross Zone Scripting Cross Zone Scripting CAPEC-108: Command Line Execution through SQL Injection Command Line Execution through SQL Injection CAPEC-109: Object Relational Mapping Injection Object Relational Mapping Injection CAPEC-110: SQL Injection through SOAP Parameter Tampering SQL Injection through SOAP Parameter Tampering CAPEC-120: Double Encoding Double Encoding CAPEC-135: Format String Injection Format String Injection CAPEC-136: LDAP Injection LDAP Injection CAPEC-153: Input Data Manipulation Input Data Manipulation CAPEC-182: Flash Injection Flash Injection CAPEC-209: XSS Using MIME Type Mismatch XSS Using MIME Type Mismatch CAPEC-230: Serialized Data with Nested Payloads Serialized Data with Nested Payloads CAPEC-231: Oversized Serialized Data Payloads Oversized Serialized Data Payloads CAPEC-250: XML Injection XML Injection CAPEC-261: Fuzzing for garnering other adjacent user/sensitive data Fuzzing for garnering other adjacent user/sensitive data CAPEC-267: Leverage Alternate Encoding Leverage Alternate Encoding CAPEC-473: Signature Spoof Signature Spoof CAPEC-588: DOM-Based XSS DOM-Based XSS CAPEC-664: Server Side Request Forgery Server Side Request Forgery
Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.10 }} 0.01%

score

0.41550

percentile

CVSS30 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability
: