{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15351 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15351 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor V9 play, published on 15 Feb 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-15351 and fix it if it is affected.\n\nWhat it is: CVE-2017-15351 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor V9 play, published on 15 Feb 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-15351 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. Honor V9 play. 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-15351/ (Markdown: https://insights.sbomify.com/CVE-2017-15351/index.md)","id":"CVE-2017-15351","markdown":"https://insights.sbomify.com/CVE-2017-15351/index.md","name":"CVE-2017-15351","record":{"aliases":["GHSA-8h4r-cwx7-rqq7"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Honor V9 play","requires_auth":"none","summary":"An attacker can bypass authentication in the Find Phone function to use the phone normally on Huawei Honor V9 play devices.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_v9_play_firmware","vendor":"huawei"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The 'Find Phone' function in Huawei Honor V9 play smart phones with versions earlier than Jimmy-AL00AC00B135 has an authentication bypass vulnerability. Due to improper authentication realization in the 'Find Phone' function. An attacker may exploit the vulnerability to bypass the 'Find Phone' function in order to use the phone normally.","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 V9 play","id":"CVE-2017-15351","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":"Missing authorization in OceanStor 2800 V3,OceanStor 5300 V3,OceanStor 5500 V3,OceanStor 5600 V3,OceanStor 5800 V3","id":"CVE-2017-15352"},"packages":[],"prev":{"headline":"Memory corruption in DP300,IPS Module,NGFW Module,NIP6300,NIP6600,NIP6800,RP200,SVN5600,SVN5800,SVN5800-C,Secospace USG6300,Secospace USG6500,Secospace USG6600,TE30,TE40,TE50,TE60,TP3206,USG9500,","id":"CVE-2017-15350"},"products":["Honor V9 play"],"published":"2018-02-15","related":[{"cvss_score":4.6,"headline":"Auth bypass in n/a","id":"CVE-2017-17145","kev_date_added":null,"published":"2018-03-09"}],"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-08-05","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An attacker can bypass authentication in the Find Phone function to use the phone normally on Huawei Honor V9 play devices.","url":"https://insights.sbomify.com/CVE-2017-15351/"}