{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-1801 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1801 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1801 is a medium-severity authentication bypass vulnerability in Mate 30 Pro;Mate 30, published on 10 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-1801 and fix it if it is affected.\n\nWhat it is: CVE-2020-1801 is a medium-severity authentication bypass vulnerability in Mate 30 Pro;Mate 30, published on 10 Apr 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-1801 in the wild and no public exploit code.\n\nAffected product: Mate 30 Pro;Mate 30. 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-1801/ (Markdown: https://insights.sbomify.com/CVE-2020-1801/index.md)","id":"CVE-2020-1801","markdown":"https://insights.sbomify.com/CVE-2020-1801/index.md","name":"CVE-2020-1801","record":{"aliases":["GHSA-fg35-c4c9-gp8p"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone","requires_auth":"none","summary":"Improper authentication in Huawei Mate 30 series allows attackers to bypass identity validation during sharing, leading to information disclosure.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_30_firmware","vendor":"huawei"},{"product":"mate_30_pro_firmware","vendor":"huawei"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"There is an improper authentication vulnerability in several smartphones. Certain function interface in the system does not sufficiently validate the caller's identity in certain share scenario, successful exploit could cause information disclosure. Affected product versions include:Mate 30 Pro versions Versions earlier than 10.0.0.205(C00E202R7P2);Mate 30 versions Versions earlier than 10.0.0.205(C00E201R7P2).","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 30 Pro;Mate 30","id":"CVE-2020-1801","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":"Other in OSCA-550;OSCA-550A;OSCA-550AX;OSCA-550X","id":"CVE-2020-1802"},"packages":[],"prev":{"headline":"Missing authorization in HUAWEI P30","id":"CVE-2020-1800"},"products":["Mate 30 Pro;Mate 30"],"published":"2020-04-10","related":[{"cvss_score":7.8,"headline":"Use after free in HUAWEI Mate 30;HUAWEI P30","id":"CVE-2020-9263","kev_date_added":null,"published":"2020-10-19"},{"cvss_score":7.8,"headline":"Memory corruption in HUAWEI Mate 30","id":"CVE-2020-9261","kev_date_added":null,"published":"2020-07-06"},{"cvss_score":7.8,"headline":"Use after free in HUAWEI Mate 30","id":"CVE-2020-9262","kev_date_added":null,"published":"2020-07-06"},{"cvss_score":6.7,"headline":"Memory corruption in HUAWEI Mate 30","id":"CVE-2021-22301","kev_date_added":null,"published":"2021-02-05"},{"cvss_score":6.7,"headline":"Memory corruption in HUAWEI Mate 30","id":"CVE-2020-9125","kev_date_added":null,"published":"2020-12-29"},{"cvss_score":6.7,"headline":"Memory corruption in HUAWEI Mate 30","id":"CVE-2020-9129","kev_date_added":null,"published":"2020-11-13"},{"cvss_score":6.5,"headline":"Information disclosure in HUAWEI Mate 30","id":"CVE-2020-1835","kev_date_added":null,"published":"2020-06-18"}],"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":"Improper authentication in Huawei Mate 30 series allows attackers to bypass identity validation during sharing, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2020-1801/"}