{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9105 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9105 is a medium-severity memory corruption vulnerability in Taurus-AN00B, published on 9 Oct 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-9105 and fix it if it is affected.\n\nWhat it is: CVE-2020-9105 is a medium-severity memory corruption vulnerability in Taurus-AN00B, published on 9 Oct 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-9105 in the wild and no public exploit code.\n\nAffected product: Taurus-AN00B. 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-9105/ (Markdown: https://insights.sbomify.com/CVE-2020-9105/index.md)","id":"CVE-2020-9105","markdown":"https://insights.sbomify.com/CVE-2020-9105/index.md","name":"CVE-2020-9105","record":{"aliases":["GHSA-vvgf-f82h-v9cv"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei mobile device","requires_auth":"high_privilege","summary":"Attackers can exploit insufficient input validation to access and modify device memory, potentially causing service abnormalities on Huawei devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"taurus-an00b_firmware","vendor":"huawei"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Taurus-AN00B versions earlier than 10.1.0.156(C00E155R7P2) have an insufficient input validation vulnerability. Due to the input validation logic is incorrect, an attacker can exploit this vulnerability to access and modify the memory of the device by doing a series of operations. Successful exploit may cause the service abnormal.","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":"Memory corruption in Taurus-AN00B","id":"CVE-2020-9105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in HUAWEI P30 Pro","id":"CVE-2020-9106"},"packages":[],"prev":{"headline":"Denial of service in HUAWEI P30","id":"CVE-2020-9104"},"products":["Taurus-AN00B"],"published":"2020-10-09","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Taurus-AN00B","id":"CVE-2020-9112","kev_date_added":null,"published":"2020-10-19"},{"cvss_score":6.5,"headline":"Memory corruption in Taurus-AN00B","id":"CVE-2020-9238","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":6.5,"headline":"Use after free in Taurus-AN00B","id":"CVE-2020-9084","kev_date_added":null,"published":"2020-09-18"},{"cvss_score":5.5,"headline":"Memory corruption in Taurus-AN00B","id":"CVE-2020-9091","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":5.5,"headline":"Memory corruption in Taurus-AN00B","id":"CVE-2020-9240","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":4.6,"headline":"Information disclosure in Taurus-AN00B","id":"CVE-2020-9110","kev_date_added":null,"published":"2020-10-12"}],"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 can exploit insufficient input validation to access and modify device memory, potentially causing service abnormalities on Huawei devices.","url":"https://insights.sbomify.com/CVE-2020-9105/"}