{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-15316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15316 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Dec 2017. 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-15316 and fix it if it is affected.\n\nWhat it is: CVE-2017-15316 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Dec 2017. 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-15316 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. Mate 9. 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-15316/ (Markdown: https://insights.sbomify.com/CVE-2017-15316/index.md)","id":"CVE-2017-15316","markdown":"https://insights.sbomify.com/CVE-2017-15316/index.md","name":"CVE-2017-15316","record":{"aliases":["GHSA-r9g8-36p4-9ggj"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 9 GPU driver","requires_auth":"none","summary":"A malicious application can trigger a double free in the GPU driver, leading to system crashes or arbitrary code execution on Huawei Mate 9 devices.","user_interaction":"required","vuln_class":"use_after_free"},"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":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-415","name":"Double Free"}],"description":"The GPU driver of Mate 9 Huawei smart phones with software before MHA-AL00B 8.0.0.334(C00) and Mate 9 Pro Huawei smart phones with software before LON-AL00B 8.0.0.334(C00) has a memory double free vulnerability. An attacker tricks a user into installing a malicious application, and the application can call special API, which triggers double free and causes a system 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","id":"CVE-2017-15316","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":"Memory corruption in AR120-S","id":"CVE-2017-15317"},"packages":[],"prev":{"headline":"Denial of service in NIP6300,NIP6600,Secospace USG6300,Secospace USG6500","id":"CVE-2017-15315"},"products":["Mate 9","Mate 9 Pro"],"published":"2017-12-22","related":[{"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-09-16","vendors":["Huawei Technologies Co., Ltd."]},"summary":"A malicious application can trigger a double free in the GPU driver, leading to system crashes or arbitrary code execution on Huawei Mate 9 devices.","url":"https://insights.sbomify.com/CVE-2017-15316/"}