{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2727 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2727 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2727 is a medium-severity authentication bypass vulnerability in Huawei P9, published on 22 Nov 2017. 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-2727 and fix it if it is affected.\n\nWhat it is: CVE-2017-2727 is a medium-severity authentication bypass vulnerability in Huawei P9, published on 22 Nov 2017. 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-2727 in the wild and no public exploit code.\n\nAffected product: Huawei P9. 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-2727/ (Markdown: https://insights.sbomify.com/CVE-2017-2727/index.md)","id":"CVE-2017-2727","markdown":"https://insights.sbomify.com/CVE-2017-2727/index.md","name":"CVE-2017-2727","record":{"aliases":["GHSA-7w3q-qffv-c74h"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei P9 smartphone","requires_auth":"none","summary":"An unauthenticated attacker can bypass phone activation to access user management and create new users, leading to privilege escalation on Huawei P9 devices.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p9_firmware","vendor":"huawei"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[],"description":"Huawei P9 smart phones with software versions earlier before EVA-AL00C00B365, versions earlier before EVA-AL10C00B365,Versions earlier before EVA-CL00C92B365, versions earlier before EVA-DL00C17B365, versions earlier before EVA-TL00C01B365 have a privilege escalation vulnerability. An unauthenticated attacker can bypass phone activation to user management page of the phone and create a new user. Successful exploit could allow the attacker operate part function of the phone.","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 Huawei P9","id":"CVE-2017-2727","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":"Auth bypass in Honor 6X","id":"CVE-2017-2728"},"packages":[],"prev":{"headline":"Memory corruption in P10 Plus,P10","id":"CVE-2017-2726"},"products":["Huawei P9"],"published":"2017-11-22","related":[{"cvss_score":6.8,"headline":"Auth bypass in Huawei P9","id":"CVE-2017-2691","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":5.5,"headline":"Information disclosure in P9","id":"CVE-2017-17319","kev_date_added":null,"published":"2018-03-20"},{"cvss_score":5.4,"headline":"Information disclosure in HUAWEI P9","id":"CVE-2017-2713","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":4.7,"headline":"Race condition in P9","id":"CVE-2017-8148","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":4.6,"headline":"Auth bypass in P9, P9 Lite EVA-AL10C00,EVA-CL10C00,EVA-DL10C00,EVA-TL10C00,VNS-L21C185,","id":"CVE-2016-8776","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":3.3,"headline":"Information disclosure in P9 EVA-AL10C00B192 and earlier versions,EVA-DL10C00B192 and earlier versions,EVA-TL10C00B192 and earlier versions,EVA-CL10C00B192 and earlier versions","id":"CVE-2016-8757","kev_date_added":null,"published":"2017-04-02"}],"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-09-16","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An unauthenticated attacker can bypass phone activation to access user management and create new users, leading to privilege escalation on Huawei P9 devices.","url":"https://insights.sbomify.com/CVE-2017-2727/"}