{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2728 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2728 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2728 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 6X, 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-2728 and fix it if it is affected.\n\nWhat it is: CVE-2017-2728 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 6X, 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-2728 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. Honor 6X. 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-2728/ (Markdown: https://insights.sbomify.com/CVE-2017-2728/index.md)","id":"CVE-2017-2728","markdown":"https://insights.sbomify.com/CVE-2017-2728/index.md","name":"CVE-2017-2728","record":{"aliases":["GHSA-r7mp-gqfh-q2fr"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Huawei Honor 6X","requires_auth":"none","summary":"Attackers can bypass screen lock on Huawei Honor 6X devices by impersonating trusted Bluetooth devices if smart unlock is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_6x_firmware","vendor":"huawei"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"Some Huawei mobile phones Honor 6X Berlin-L22C636B150 and earlier versions have a Bluetooth unlock bypassing vulnerability. If a user has enabled the smart unlock function, an attacker can impersonate the user's Bluetooth device to unlock the user's mobile phone screen.uawei mobile phones have a Bluetooth unlock bypassing vulnerability due to the lack of validation on Bluetooth devices. If a user has enabled the smart unlock function, an attacker can impersonate the user's Bluetooth device to unlock the user's mobile phone screen.","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 Honor 6X","id":"CVE-2017-2728","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Honor 5A","id":"CVE-2017-2729"},"packages":[],"prev":{"headline":"Auth bypass in Huawei P9","id":"CVE-2017-2727"},"products":["Honor 6X"],"published":"2017-11-22","related":[{"cvss_score":5.5,"headline":"Information disclosure in Honor 6X","id":"CVE-2017-2733","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":"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":"Attackers can bypass screen lock on Huawei Honor 6X devices by impersonating trusted Bluetooth devices if smart unlock is enabled.","url":"https://insights.sbomify.com/CVE-2017-2728/"}