{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1835 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1835 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1835 is a medium-severity vulnerability in HUAWEI Mate 30, published on 18 Jun 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-1835 and fix it if it is affected.\n\nWhat it is: CVE-2020-1835 is a medium-severity vulnerability in HUAWEI Mate 30, published on 18 Jun 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-1835 in the wild and no public exploit code.\n\nAffected product: HUAWEI 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-1835/ (Markdown: https://insights.sbomify.com/CVE-2020-1835/index.md)","id":"CVE-2020-1835","markdown":"https://insights.sbomify.com/CVE-2020-1835/index.md","name":"CVE-2020-1835","record":{"aliases":["GHSA-7vvx-6q94-66wq"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate 30","requires_auth":"none","summary":"An attacker with authenticated Bluetooth access can exploit a logic error to disclose sensitive information on Huawei Mate 30 devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_30_firmware","vendor":"huawei"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"HUAWEI Mate 30 with versions earlier than 10.1.0.126(C00E125R5P3) have an information disclosure vulnerability. A logic judgment error occurs when the system handling Bluetooth connections, an attacker could craft as an authenticated Bluetooth peer 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":"Information disclosure in HUAWEI Mate 30","id":"CVE-2020-1835","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":"Information disclosure in HUAWEI P30;HUAWEI P30 Pro","id":"CVE-2020-1836"},"packages":[],"prev":{"headline":"Code injection in HUAWEI P30;HUAWEI P30 Pro","id":"CVE-2020-1834"},"products":["HUAWEI Mate 30"],"published":"2020-06-18","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"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker with authenticated Bluetooth access can exploit a logic error to disclose sensitive information on Huawei Mate 30 devices.","url":"https://insights.sbomify.com/CVE-2020-1835/"}