{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2707 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2707 is a high-severity vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Nov 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-2707 and fix it if it is affected.\n\nWhat it is: CVE-2017-2707 is a high-severity vulnerability in Huawei Technologies Co., Ltd. Mate 9, published on 22 Nov 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-2707 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-2707/ (Markdown: https://insights.sbomify.com/CVE-2017-2707/index.md)","id":"CVE-2017-2707","markdown":"https://insights.sbomify.com/CVE-2017-2707/index.md","name":"CVE-2017-2707","record":{"aliases":["GHSA-8xc6-v3h5-gr99"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 9","requires_auth":"none","summary":"An attacker can escalate privileges to delete messages or send messages as the user on Huawei Mate 9 devices via the Push module.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_firmware","vendor":"huawei"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"Mate 9 smartphones with software MHA-AL00AC00B125 have a privilege escalation vulnerability in Push module. An attacker tricks a user to save a rich media into message on the smart phone, which could be exploited to cause the attacker to delete message or fake user to send message.","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":"Privilege escalation in Mate 9","id":"CVE-2017-2707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Nice","id":"CVE-2017-2708"},"packages":[],"prev":{"headline":"Path traversal in Mate 9","id":"CVE-2017-2706"},"products":["Mate 9"],"published":"2017-11-22","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":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 escalate privileges to delete messages or send messages as the user on Huawei Mate 9 devices via the Push module.","url":"https://insights.sbomify.com/CVE-2017-2707/"}