{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17173 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17173 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17173 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-17173 and fix it if it is affected.\n\nWhat it is: CVE-2017-17173 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 14 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-17173 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. 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-17173/ (Markdown: https://insights.sbomify.com/CVE-2017-17173/index.md)","id":"CVE-2017-17173","markdown":"https://insights.sbomify.com/CVE-2017-17173/index.md","name":"CVE-2017-17173","record":{"aliases":["GHSA-gmcx-8jp4-4q98"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone driver","requires_auth":"none","summary":"A malicious app can trigger an arbitrary memory free in the GPU driver, leading to phone crashes or arbitrary code execution on Huawei Mate 9 Pro devices.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_pro_fimware","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Due to insufficient parameters verification GPU driver of Mate 9 Pro Huawei smart phones with the versions before LON-AL00B 8.0.0.356(C00) has an arbitrary memory free vulnerability. An attacker can tricks a user into installing a malicious application on the smart phone, and send given parameter to driver to release special kernel memory resource. Successful exploit may result in phone crash or arbitrary code execution.","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":"Use after free in Mate 9 Pro","id":"CVE-2017-17173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in RSE6500; SoftCo; VP9660; eSpace U1981","id":"CVE-2017-17174"},"packages":[],"prev":{"headline":"Privilege escalation in LYO-L21","id":"CVE-2017-17172"},"products":["Mate 9 Pro"],"published":"2018-06-14","related":[{"cvss_score":5.5,"headline":"Information disclosure in Mate 9 Pro","id":"CVE-2019-5244","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":4.6,"headline":"Auth bypass in Mate 9 Pro","id":"CVE-2017-17326","kev_date_added":null,"published":"2018-03-09"}],"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 malicious app can trigger an arbitrary memory free in the GPU driver, leading to phone crashes or arbitrary code execution on Huawei Mate 9 Pro devices.","url":"https://insights.sbomify.com/CVE-2017-17173/"}