{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9073 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9073 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9073 is a low-severity authentication bypass vulnerability in P20, published on 15 May 2020. 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-2020-9073 and fix it if it is affected.\n\nWhat it is: CVE-2020-9073 is a low-severity authentication bypass vulnerability in P20, published on 15 May 2020. 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-2020-9073 in the wild and no public exploit code.\n\nAffected product: P20. 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-2020-9073/ (Markdown: https://insights.sbomify.com/CVE-2020-9073/index.md)","id":"CVE-2020-9073","markdown":"https://insights.sbomify.com/CVE-2020-9073/index.md","name":"CVE-2020-9073","record":{"aliases":["GHSA-48xv-3rm6-fh3c"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei P20 smartphone","requires_auth":"none","summary":"Attackers with physical access can bypass student mode restrictions on Huawei P20 devices due to insufficient identity validation.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p20_firmware","vendor":"huawei"}],"cvss":{"score":2.4,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Huawei P20 smartphones with versions earlier than 10.0.0.156(C00E156R1P4) have an improper authentication vulnerability. The vulnerability is due to that when an user wants to do certain operation, the software insufficiently validate the user's identity. Attackers need to physically access the smartphone to exploit this vulnerability. Successful exploit could allow the attacker to bypass the limit of student mode function.","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 P20","id":"CVE-2020-9073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in HONOR 20","id":"CVE-2020-9074"},"packages":[],"prev":{"headline":"Privilege escalation in OSD","id":"CVE-2020-9072"},"products":["P20"],"published":"2020-05-15","related":[{"cvss_score":5.9,"headline":"Memory corruption in Huawei P20","id":"CVE-2018-7987","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":5.7,"headline":"Other in P20","id":"CVE-2019-5211","kev_date_added":null,"published":"2019-11-29"},{"cvss_score":5.5,"headline":"Missing authorization in P20","id":"CVE-2019-5212","kev_date_added":null,"published":"2019-11-29"},{"cvss_score":4.6,"headline":"Security feature bypass in P20","id":"CVE-2019-5283","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":4.6,"headline":"Security feature bypass in P20","id":"CVE-2019-5306","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":"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-04","vendors":["n/a"]},"summary":"Attackers with physical access can bypass student mode restrictions on Huawei P20 devices due to insufficient identity validation.","url":"https://insights.sbomify.com/CVE-2020-9073/"}