{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1806 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1806 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1806 is a high-severity vulnerability in Huawei Honor V10, published on 27 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-1806 and fix it if it is affected.\n\nWhat it is: CVE-2020-1806 is a high-severity vulnerability in Huawei Honor V10, published on 27 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-1806 in the wild and no public exploit code.\n\nAffected product: Huawei Honor V10. 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-1806/ (Markdown: https://insights.sbomify.com/CVE-2020-1806/index.md)","id":"CVE-2020-1806","markdown":"https://insights.sbomify.com/CVE-2020-1806/index.md","name":"CVE-2020-1806","record":{"aliases":["GHSA-j43g-xjfm-r8v4"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Honor V10","requires_auth":"none","summary":"Out-of-bounds read in Huawei Honor V10 drivers allows attackers to disclose information or cause service abnormalities.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_v10_firmware","vendor":"huawei"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities. Certain driver program does not sufficiently validate certain parameters received, that would lead to several bytes out of bound read. Successful exploit may cause information disclosure or service abnormal. This is 3 out of 3 out of bounds vulnerabilities found. Different than CVE-2020-1804 and CVE-2020-1805.","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":"Information disclosure in Honor V10","id":"CVE-2020-1806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in HUAWEI Mate 20","id":"CVE-2020-1807"},"packages":[],"prev":{"headline":"Information disclosure in Honor V10","id":"CVE-2020-1805"},"products":["Honor V10"],"published":"2020-04-27","related":[{"cvss_score":7.1,"headline":"Information disclosure in Honor V10","id":"CVE-2020-1804","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":7.1,"headline":"Information disclosure in Honor V10","id":"CVE-2020-1805","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":5.5,"headline":"Memory corruption in Honor V10","id":"CVE-2020-1792","kev_date_added":null,"published":"2020-02-28"}],"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":"Out-of-bounds read in Huawei Honor V10 drivers allows attackers to disclose information or cause service abnormalities.","url":"https://insights.sbomify.com/CVE-2020-1806/"}