{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15347 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15347 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15347 is a medium-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 15 Feb 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-15347 and fix it if it is affected.\n\nWhat it is: CVE-2017-15347 is a medium-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 15 Feb 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-15347 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-15347/ (Markdown: https://insights.sbomify.com/CVE-2017-15347/index.md)","id":"CVE-2017-15347","markdown":"https://insights.sbomify.com/CVE-2017-15347/index.md","name":"CVE-2017-15347","record":{"aliases":["GHSA-hp8r-934f-8wjx"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 9 Pro","requires_auth":"none","summary":"A local attacker can cause a crash on Huawei Mate 9 Pro devices by tricking users into installing a malicious application that triggers a use-after-free vulnerability.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_pro_firmware","vendor":"huawei"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Huawei Mate 9 Pro mobile phones with software of versions earlier than LON-AL00BC00B235 have a use after free (UAF) vulnerability. An attacker tricks a user into installing a malicious application, and the application can riggers access memory after free it. A local attacker may exploit this vulnerability to cause the mobile phone to crash.","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-15347","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":"Denial of service in IPS Module,NGFW Module,NIP6300,NIP6600,Secospace USG6300,Secospace USG6500,Secospace USG6600,USG9500,","id":"CVE-2017-15348"},"packages":[],"prev":{"headline":"Denial of service in S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210 TD","id":"CVE-2017-15346"},"products":["Mate 9 Pro"],"published":"2018-02-15","related":[{"cvss_score":8.8,"headline":"Memory corruption in Mate 9 Pro","id":"CVE-2017-17225","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":7.8,"headline":"Use after free in Mate 9 Pro","id":"CVE-2017-17320","kev_date_added":null,"published":"2018-03-20"},{"cvss_score":7.8,"headline":"Integer overflow in Mate 9 Pro","id":"CVE-2017-17324","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":5.5,"headline":"Auth bypass in Mate 9 Pro","id":"CVE-2017-17279","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":4.6,"headline":"Auth bypass in Mate 9 Pro","id":"CVE-2019-5217","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":4.6,"headline":"Auth bypass in Huawei nova 2 Plus, Huawei Mate9 Pro","id":"CVE-2018-7988","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":"A local attacker can cause a crash on Huawei Mate 9 Pro devices by tricking users into installing a malicious application that triggers a use-after-free vulnerability.","url":"https://insights.sbomify.com/CVE-2017-15347/"}