{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17326 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17326 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17326 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 9 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17326 and fix it if it is affected.\n\nWhat it is: CVE-2017-17326 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 9 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17326 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-17326/ (Markdown: https://insights.sbomify.com/CVE-2017-17326/index.md)","id":"CVE-2017-17326","markdown":"https://insights.sbomify.com/CVE-2017-17326/index.md","name":"CVE-2017-17326","record":{"aliases":["GHSA-qw3f-pqc2-mc9h"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Huawei Mate 9 Pro","requires_auth":"none","summary":"Attackers can bypass activation lock on Huawei Mate 9 Pro devices with Find My Phone enabled, allowing unauthorized activation with a new account.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_9_pro_fimware","vendor":"huawei"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"Huawei Mate 9 Pro Smartphones with software of LON-AL00BC00B139D; LON-AL00BC00B229 have an activation lock bypass vulnerability. The smartphone is supposed to be activated by the former account after reset if find my phone function is on. The software does not have a sufficient protection of activation lock. Successful exploit could allow an attacker to bypass the activation lock and activate the smartphone by a new account after a series of operation.","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":"Auth bypass in Mate 9 Pro","id":"CVE-2017-17326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in MHA-AL00A","id":"CVE-2017-17327"},"packages":[],"prev":{"headline":"Information disclosure in HiCinema","id":"CVE-2017-17325"},"products":["Mate 9 Pro"],"published":"2018-03-09","related":[{"cvss_score":7.8,"headline":"Use after free in Mate 9 Pro","id":"CVE-2017-17173","kev_date_added":null,"published":"2018-06-14"},{"cvss_score":5.5,"headline":"Information disclosure in Mate 9 Pro","id":"CVE-2019-5244","kev_date_added":null,"published":"2019-06-04"}],"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":"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":"Attackers can bypass activation lock on Huawei Mate 9 Pro devices with Find My Phone enabled, allowing unauthorized activation with a new account.","url":"https://insights.sbomify.com/CVE-2017-17326/"}