{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-17221 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17221 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17221 is a high-severity code injection vulnerability in Huawei Technologies Co., Ltd. eSpace 7950; eSpace 8950, published on 9 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17221 and fix it if it is affected.\n\nWhat it is: CVE-2017-17221 is a high-severity code injection vulnerability in Huawei Technologies Co., Ltd. eSpace 7950; eSpace 8950, published on 9 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17221 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. eSpace 7950; eSpace 8950. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-17221/ (Markdown: https://insights.sbomify.com/CVE-2017-17221/index.md)","id":"CVE-2017-17221","markdown":"https://insights.sbomify.com/CVE-2017-17221/index.md","name":"CVE-2017-17221","record":{"aliases":["GHSA-c9p4-jv2v-5g2x"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei IP phone","requires_auth":"low_privilege","summary":"An authenticated remote attacker can execute arbitrary code on Huawei eSpace phones by sending crafted packets after uploading a signal tone.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"espace_7950_firmware","vendor":"huawei"},{"product":"espace_8950_firmware","vendor":"huawei"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Import Signal Tone function in Huawei eSpace 7950 V200R003C30; eSpace 8950 V200R003C00; V200R003C30 has a remote code execution vulnerability. An authenticated, remote attacker can craft and send the packets to the affected products after the Signal Tone is uploaded. Due to insufficient verification of the packets, this could be exploited to execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Code injection in eSpace 7950; eSpace 8950","id":"CVE-2017-17221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in eSpace 7950; eSpace 8950","id":"CVE-2017-17222"},"packages":[],"prev":{"headline":"Memory corruption in DP300; RP200; TE30; TE40; TE50; TE60","id":"CVE-2017-17220"},"products":["eSpace 7950; eSpace 8950"],"published":"2018-03-09","related":[{"cvss_score":8.8,"headline":"Code injection in eSpace 7950; eSpace 8950","id":"CVE-2017-17222","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":7.4,"headline":"Security feature bypass in eSpace 7950","id":"CVE-2018-7958","kev_date_added":null,"published":"2018-11-27"},{"cvss_score":7.4,"headline":"Information disclosure in eSpace 7950","id":"CVE-2018-7960","kev_date_added":null,"published":"2018-11-27"},{"cvss_score":5.9,"headline":"Weak cryptography in eSpace 7950","id":"CVE-2018-7959","kev_date_added":null,"published":"2018-11-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An authenticated remote attacker can execute arbitrary code on Huawei eSpace phones by sending crafted packets after uploading a signal tone.","url":"https://insights.sbomify.com/CVE-2017-17221/"}