{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17320 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 20 Mar 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-17320 and fix it if it is affected.\n\nWhat it is: CVE-2017-17320 is a high-severity use after free vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 20 Mar 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-17320 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-17320/ (Markdown: https://insights.sbomify.com/CVE-2017-17320/index.md)","id":"CVE-2017-17320","markdown":"https://insights.sbomify.com/CVE-2017-17320/index.md","name":"CVE-2017-17320","record":{"aliases":["GHSA-9w3x-5xrr-jfm6"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 9 Pro","requires_auth":"none","summary":"A double free vulnerability in Huawei Mate 9 Pro allows malicious code execution if a user with root privileges installs a crafted application.","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":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":"Huawei Mate 9 Pro smartphones with software of LON-AL00BC00B139D, LON-AL00BC00B229, LON-L29DC721B188 have a memory double free vulnerability. The system does not manage the memory properly, that frees on the same memory address twice. An attacker tricks the user who has root privilege to install a crafted application, successful exploit could result in malicious 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-17320","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 eNSP","id":"CVE-2017-17321"},"packages":[],"prev":{"headline":"Information disclosure in P9","id":"CVE-2017-17319"},"products":["Mate 9 Pro"],"published":"2018-03-20","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":"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":5.5,"headline":"Use after free in Mate 9 Pro","id":"CVE-2017-15347","kev_date_added":null,"published":"2018-02-15"},{"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 double free vulnerability in Huawei Mate 9 Pro allows malicious code execution if a user with root privileges installs a crafted application.","url":"https://insights.sbomify.com/CVE-2017-17320/"}