{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1803 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1803 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1803 is a medium-severity authentication bypass vulnerability in Huawei Honor V20, published on 20 Apr 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-1803 and fix it if it is affected.\n\nWhat it is: CVE-2020-1803 is a medium-severity authentication bypass vulnerability in Huawei Honor V20, published on 20 Apr 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-1803 in the wild and no public exploit code.\n\nAffected product: Huawei Honor V20. 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-1803/ (Markdown: https://insights.sbomify.com/CVE-2020-1803/index.md)","id":"CVE-2020-1803","markdown":"https://insights.sbomify.com/CVE-2020-1803/index.md","name":"CVE-2020-1803","record":{"aliases":["GHSA-784w-qwm8-7p5h"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Honor V20","requires_auth":"none","summary":"Insufficient identity validation for smart wearables allows attackers with local access to disclose information on Huawei Honor V20 devices.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_v20_firmware","vendor":"huawei"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Huawei smartphones Honor V20 with versions earlier than 10.0.0.179(C636E3R4P3),versions earlier than 10.0.0.180(C185E3R3P3),versions earlier than 10.0.0.180(C432E10R3P4) have an information disclosure vulnerability. The device does not sufficiently validate the identity of smart wearable device in certain specific scenario, the attacker need to gain certain information in the victim's smartphone to launch the attack, successful exploit could cause information disclosure.","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 V20","id":"CVE-2020-1803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Honor V10","id":"CVE-2020-1804"},"packages":[],"prev":{"headline":"Other in OSCA-550;OSCA-550A;OSCA-550AX;OSCA-550X","id":"CVE-2020-1802"},"products":["Honor V20"],"published":"2020-04-20","related":[{"cvss_score":7.8,"headline":"Race condition in P30, P30 Pro, Honor V20","id":"CVE-2019-5228","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":3.3,"headline":"Information disclosure in Honor V20","id":"CVE-2019-5301","kev_date_added":null,"published":"2019-08-08"}],"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":["Huawei"]},"summary":"Insufficient identity validation for smart wearables allows attackers with local access to disclose information on Huawei Honor V20 devices.","url":"https://insights.sbomify.com/CVE-2020-1803/"}