{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-17176 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17176 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro, published on 17 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17176 and fix it if it is affected.\n\nWhat it is: CVE-2017-17176 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro, published on 17 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17176 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro. 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-17176/ (Markdown: https://insights.sbomify.com/CVE-2017-17176/index.md)","id":"CVE-2017-17176","markdown":"https://insights.sbomify.com/CVE-2017-17176/index.md","name":"CVE-2017-17176","record":{"aliases":["GHSA-2p9x-qhg2-q4vr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone firmware","requires_auth":"high_privilege","summary":"A root-privileged attacker can exploit a memory corruption flaw in the hardware security module to execute arbitrary code in TrustZone.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_firmware","vendor":"huawei"},{"product":"mate_9_pro_firmware","vendor":"huawei"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"The hardware security module of Mate 9 and Mate 9 Pro Huawei smart phones with the versions earlier before MHA-AL00BC00B156, versions earlier before MHA-CL00BC00B156, versions earlier before MHA-DL00BC00B156, versions earlier before MHA-TL00BC00B156, versions earlier before LON-AL00BC00B156, versions earlier before LON-CL00BC00B156, versions earlier before LON-DL00BC00B156, versions earlier before LON-TL00BC00B156 has a arbitrary memory read/write vulnerability due to the input parameters validation. An attacker with the root privilege of the Android system could exploit this vulnerability to read and write memory data anywhere or execute arbitrary code in the TrustZone.","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":"Memory corruption in Mate 9, Mate 9 Pro","id":"CVE-2017-17176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-17177"},"packages":[],"prev":{"headline":"Denial of service in Mate 9 Pro","id":"CVE-2017-17175"},"products":["Mate 9, Mate 9 Pro"],"published":"2018-10-17","related":[{"cvss_score":7.8,"headline":"Use after free in Mate 9","id":"CVE-2017-15316","kev_date_added":null,"published":"2017-12-22"},{"cvss_score":7.8,"headline":"Memory corruption in Mate 9","id":"CVE-2017-2716","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":7.8,"headline":"Use after free in Mate 9, Mate 9 Pro","id":"CVE-2017-8142","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":7.1,"headline":"Path traversal in Mate 9","id":"CVE-2017-2706","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":7.1,"headline":"Privilege escalation in Mate 9","id":"CVE-2017-2707","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":6.8,"headline":"Auth bypass in Mate 9","id":"CVE-2017-2702","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":6.8,"headline":"Auth bypass in Mate 9, P9","id":"CVE-2017-2703","kev_date_added":null,"published":"2017-11-22"}],"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":"A root-privileged attacker can exploit a memory corruption flaw in the hardware security module to execute arbitrary code in TrustZone.","url":"https://insights.sbomify.com/CVE-2017-17176/"}