# CVE-2017-17301: Weak cryptography in AR120-S,AR1200,AR1200-S,AR150,AR160,AR200,AR200-S,AR2200,AR2200-S,AR3200,AR3600,AR510,CloudEngine 12800,CloudEngine 5800,CloudEngine 6800,CloudEngine 7800,DP300,SMC2.0,SRG1300,SRG2300,SRG3300,TE30,TE60,VP9660,ViewPoint 8660,eSpace IAD,eSpace U1981,eSpace USM > An unauthenticated remote attacker can forge RSA certificates due to weak cryptography, bypassing security controls on Huawei network devices. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 15 Feb 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-7vg8-9cq4-jmgg ## What is CVE-2017-17301? CVE-2017-17301 is a critical vulnerability in Huawei Ar3200 Firmware, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Huawei AR120-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR1200 V200R005C20, V200R005C32, V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, AR1200-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, AR160 V200R005C32, V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, AR200 V200R005C32, V200R006C10, V200R007C00, V200R007C01, V200R008C20, AR200-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR2200 V200R005C20, V200R005C32, V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, AR2200-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR3200 V200R005C32, V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR3600 V200R006C10, V200R007C00, V200R007C01, V200R008C20, AR510 V200R005C32, V200R006C10, V200R007C00, V200R008C20, CloudEngine 12800 V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00, V200R001C00, CloudEngine 5800 V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00, V200R001C00, CloudEngine 6800 V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00, V200R001C00, CloudEngine 7800 V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00, V200R001C00, DP300 V500R002C00, SMC2.0 V100R003C10, V100R005C00, V500R002C00, SRG1300 V200R005C32, V200R006C10, V200R007C00, V200R007C02, V200R008C20, SRG2300 V200R005C32, V200R006C10, V200R007C00, V200R007C02, V200R008C20, SRG3300 V200R005C32, V200R006C10, V200R007C00, V200R008C20, TE30 V100R001C10, TE60 V100R003C00, V500R002C00, VP9660 V200R001C02, V200R001C30, V500R002C00, ViewPoint 8660 V100R008C02, V100R008C03, eSpace IAD V300R002C01, eSpace U1981 V200R003C20, V200R003C30, eSpace USM V100R001C01, V300R001C00 have a weak cryptography vulnerability. Due to not properly some values in the certificates, an unauthenticated remote attacker could forges a specific RSA certificate and exploits the vulnerability to pass identity authentication and logs into the target device to obtain permissions configured for the specific user name. Weakness: CWE-295 (Improper Certificate Validation) ## Which versions are affected by CVE-2017-17301? It affects 28 products. Products: Huawei Ar120-S Firmware, Huawei Ar1200-S Firmware, Huawei Ar1200 Firmware, Huawei Ar150 Firmware, Huawei Ar160 Firmware, Huawei Ar200-S Firmware, Huawei Ar200 Firmware, Huawei Ar2200-S Firmware, Huawei Ar2200 Firmware, Huawei Ar3200 Firmware, Huawei Ar3600 Firmware, Huawei Ar510 Firmware, Huawei Cloudengine 12800 Firmware, Huawei Cloudengine 5800 Firmware, Huawei Cloudengine 6800 Firmware, Huawei Cloudengine 7800 Firmware, Huawei Dp300 Firmware, Huawei Espace Iad Firmware, Huawei Espace U1981 Firmware, Huawei Espace Usm Firmware and 8 more. ## How do I fix CVE-2017-17301? No fix has been published for CVE-2017-17301 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-17301 being exploited? There is no known exploitation of CVE-2017-17301 in the wild and no public exploit code. ## Other vulnerabilities in Huawei Ar3200 Firmware - [CVE-2019-19415](https://insights.sbomify.com/CVE-2019-19415/): Denial of service in AR120-S (high 7.5) - [CVE-2019-19416](https://insights.sbomify.com/CVE-2019-19416/): Denial of service in AR120-S (high 7.5) - [CVE-2019-19417](https://insights.sbomify.com/CVE-2019-19417/): Denial of service in AR120-S (high 7.5) - [CVE-2019-5304](https://insights.sbomify.com/CVE-2019-5304/): Denial of service in AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR2200-S;AR3200;AR3600;IPS Module;NGFW Module;NIP6300;NIP6600;NetEngine16EX;S5700;S6700;SRG1300;SRG2300;SRG3300;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600 (high 7.5) - [CVE-2019-5294](https://insights.sbomify.com/CVE-2019-5294/): Memory corruption in AR120-S,AR1200,AR1200-S,AR150,AR150-S,AR160,AR200,AR200-S,AR2200,AR2200-S,AR3200,AR3600,NetEngine16EX,SRG1300,SRG2300,SRG3300 (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-17301 and fix it if it is affected. What it is: CVE-2017-17301 is a critical vulnerability in Huawei Ar3200 Firmware, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-17301 in the wild and no public exploit code. Affected product: Huawei Ar3200 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-17301/ (Markdown: https://insights.sbomify.com/CVE-2017-17301/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17301 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17301 - OSV: https://osv.dev/vulnerability/CVE-2017-17301 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-17301/ Summaries are generated and may contain mistakes; the official description above is the record.