{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8165 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8165 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8165 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 5 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-8165 and fix it if it is affected.\n\nWhat it is: CVE-2017-8165 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 5 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-8165 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-8165/ (Markdown: https://insights.sbomify.com/CVE-2017-8165/index.md)","id":"CVE-2017-8165","markdown":"https://insights.sbomify.com/CVE-2017-8165/index.md","name":"CVE-2017-8165","record":{"aliases":["GHSA-hm8r-cqhg-w4cp"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 9","requires_auth":"none","summary":"An attacker can leak sensitive information by tricking a user into installing a malicious application on Huawei Mate 9 devices.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_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:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Mate 9 Huawei smart phones with versions earlier than MHA-AL00BC00B233 have a sensitive information leak vulnerability. An attacker can trick a user to install a malicious application to exploit this vulnerability. Successful exploitation may cause sensitive information leak.","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":"Information disclosure in Mate 9","id":"CVE-2017-8165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Honor V9","id":"CVE-2017-8166"},"packages":[],"prev":{"headline":"Denial of service in EVA-AL10; EVA-CL00; EVA-DL00; EVA-L09; EVA-L19; EVA-L29; EVA-TL00; VIE-L09; VIE-L29","id":"CVE-2017-8164"},"products":["Mate 9"],"published":"2018-03-05","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-09-17","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An attacker can leak sensitive information by tricking a user into installing a malicious application on Huawei Mate 9 devices.","url":"https://insights.sbomify.com/CVE-2017-8165/"}