CVE-2017-17291
Last modified
CVE-2017-17291 is a vulnerability of currently unknown severity. Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR1200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR150-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR160 V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR200 V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30, AR200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR2200 V200R006C10, V200R006C13, V200R006C16, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR3600 V200R006C10, V200R007C00, V200R007C01, V200R008C20, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, MAX PRESENCE V100R001C00, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00, V600R006C00, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, V100R002C10 have a memory leak vulnerability. An authenticated, local attacker may craft a specific XML file to the affected products. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR1200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR150-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR160 V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR200 V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30, AR200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR2200 V200R006C10, V200R006C13, V200R006C16, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR3600 V200R006C10, V200R007C00, V200R007C01, V200R008C20, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, MAX PRESENCE V100R001C00, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00, V600R006C00, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, TE30 V100R001C02, V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, V100R002C10 have a memory leak vulnerability. An authenticated, local attacker may craft a specific XML file to the affected products. Due to not free the memory to parse the XML file, successful exploit will result in memory leak of the affected products.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Huawei | Ar120-S Firmware | v200r006c10 |
| Huawei | Ar120-S Firmware | v200r007c00 |
| Huawei | Ar120-S Firmware | v200r008c20 |
| Huawei | Ar120-S Firmware | v200r008c30 |
| Huawei | Ar1200 Firmware | v200r006c10 |
| Huawei | Ar1200 Firmware | v200r006c13 |
| Huawei | Ar1200 Firmware | v200r007c00 |
| Huawei | Ar1200 Firmware | v200r007c01 |
| Huawei | Ar1200 Firmware | v200r007c02 |
| Huawei | Ar1200 Firmware | v200r008c20 |
| Huawei | Ar1200 Firmware | v200r008c30 |
| Huawei | Ar1200-S Firmware | v200r006c10 |
| Huawei | Ar1200-S Firmware | v200r007c00 |
| Huawei | Ar1200-S Firmware | v200r008c20 |
| Huawei | Ar1200-S Firmware | v200r008c30 |
| Huawei | Ar150 Firmware | v200r006c10 |
| Huawei | Ar150 Firmware | v200r007c00 |
| Huawei | Ar150 Firmware | v200r007c01 |
| Huawei | Ar150 Firmware | v200r007c02 |
| Huawei | Ar150 Firmware | v200r008c20 |
| Huawei | Ar150 Firmware | v200r008c30 |
| Huawei | Ar150-S Firmware | v200r006c10 |
| Huawei | Ar150-S Firmware | v200r007c00 |
| Huawei | Ar150-S Firmware | v200r008c20 |
| Huawei | Ar150-S Firmware | v200r008c30 |
| Huawei | Ar160 Firmware | v200r006c10 |
| Huawei | Ar160 Firmware | v200r006c12 |
| Huawei | Ar160 Firmware | v200r007c00 |
| Huawei | Ar160 Firmware | v200r007c01 |
| Huawei | Ar160 Firmware | v200r007c02 |
| Huawei | Ar160 Firmware | v200r008c20 |
| Huawei | Ar160 Firmware | v200r008c30 |
| Huawei | Ar200 Firmware | v200r006c10 |
| Huawei | Ar200 Firmware | v200r007c00 |
| Huawei | Ar200 Firmware | v200r007c01 |
| Huawei | Ar200 Firmware | v200r008c20 |
| Huawei | Ar200 Firmware | v200r008c30 |
| Huawei | Ar200-S Firmware | v200r006c10 |
| Huawei | Ar200-S Firmware | v200r007c00 |
| Huawei | Ar200-S Firmware | v200r008c20 |
| Huawei | Ar200-S Firmware | v200r008c30 |
| Huawei | Ar2200 Firmware | v200r006c10 |
| Huawei | Ar2200 Firmware | v200r006c13 |
| Huawei | Ar2200 Firmware | v200r006c16 |
| Huawei | Ar2200 Firmware | v200r007c00 |
| Huawei | Ar2200 Firmware | v200r007c01 |
| Huawei | Ar2200 Firmware | v200r007c02 |
| Huawei | Ar2200 Firmware | v200r008c20 |
| Huawei | Ar2200 Firmware | v200r008c30 |
| Huawei | Ar2200-S Firmware | v200r006c10 |
Showing 50 of 112 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-17291?
How severe is CVE-2017-17291?
How do I fix CVE-2017-17291?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-17286Huawei AR120-S V200R005C32, V200R006C10, V200R007C00, V200R0…
- CVE-2017-17287Huawei AR120-S V200R005C32, V200R006C10, V200R007C00, V200R0…
- CVE-2017-17288Huawei DP300 V500R002C00, RP200 V500R002C00, V600R006C00, TE…
- CVE-2017-17289Huawei DP300 V500R002C00, RP200 V500R002C00, V600R006C00, TE…
- CVE-2017-1729IBM Rational Quality Manager 5.0 through 5.0.2 and 6.0 throu…5.4
- CVE-2017-17290The Light Directory Access Protocol (LDAP) clients of Huawei…
- CVE-2017-17292Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-17293Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-17294Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-17295Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-17296Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-17297Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
Are you affected by CVE-2017-17291?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
