CVE-2017-15332
Last modified
CVE-2017-15332 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, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, IPS Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, MAX PRESENCE V100R001C00, NGFW Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R002C00, V500R002C10, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00SPC200, V600R006C00, RSE6500 V500R002C00, SMC2.0 V100R003C10, V100R005C00, V500R002C00, V500R002C00T, V600R006C00, V600R006C00T, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10, SVN5800-C V200R003C00, V200R003C10, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, USG9500 V500R001C00, V500R001C20, V500R001C30, V500R001C50, USG9520 V300R001C01, V300R001C20, USG9560 V300R001C01, V300R001C20, USG9580 V300R001C01, V300R001C20, ViewPoint 9030 V100R011C02, V100R011C03, have a memory leak vulnerability in H323 protocol. The vulnerability is due to insufficient verification of the packets. EPSS estimates a 1.48% 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, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, IPS Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, MAX PRESENCE V100R001C00, NGFW Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R002C00, V500R002C10, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00SPC200, V600R006C00, RSE6500 V500R002C00, SMC2.0 V100R003C10, V100R005C00, V500R002C00, V500R002C00T, V600R006C00, V600R006C00T, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10, SVN5800-C V200R003C00, V200R003C10, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, USG9500 V500R001C00, V500R001C20, V500R001C30, V500R001C50, USG9520 V300R001C01, V300R001C20, USG9560 V300R001C01, V300R001C20, USG9580 V300R001C01, V300R001C20, ViewPoint 9030 V100R011C02, V100R011C03, have a memory leak vulnerability in H323 protocol. The vulnerability is due to insufficient verification of the packets. An unauthenticated, remote attacker could exploit this vulnerability by sending crafted packets. A successful exploit could cause a memory leak and eventual denial of service (DoS) condition on an affected device.
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 | v200r006c16pwe |
| 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 168 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15332?
How severe is CVE-2017-15332?
How do I fix CVE-2017-15332?
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-15327S12700 V200R005C00, V200R006C00, V200R006C01, V200R007C00, V…
- CVE-2017-15328Huawei HG8245H version earlier than V300R018C00SPC110 has an…
- CVE-2017-15329Huawei UMA V200R001C00 has a SQL injection vulnerability in …
- CVE-2017-1533IBM Security Access Manager Appliance 9.0.3 is vulnerable to…
- CVE-2017-15330The Flp Driver in some Huawei smartphones of the software Vi…
- CVE-2017-15331Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R0…
- CVE-2017-15333XML parser in Huawei S12700 V200R005C00,S1700 V200R009C00, V…
- CVE-2017-15334The SIP backup feature in Huawei DP300 V500R002C00, IPS Modu…
- CVE-2017-15335The SIP backup feature in Huawei DP300 V500R002C00, IPS Modu…
- CVE-2017-15336The SIP backup feature in Huawei DP300 V500R002C00, IPS Modu…
- CVE-2017-15337The SIP module in Huawei DP300 V500R002C00, IPS Module V100R…
- CVE-2017-15338The SIP module in Huawei DP300 V500R002C00, IPS Module V100R…
Are you affected by CVE-2017-15332?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
