{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-1834 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1834 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1834 is a medium-severity code injection vulnerability in HUAWEI P30;HUAWEI P30 Pro, 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-1834 and fix it if it is affected.\n\nWhat it is: CVE-2020-1834 is a medium-severity code injection vulnerability in HUAWEI P30;HUAWEI P30 Pro, 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-1834 in the wild and no public exploit code.\n\nAffected product: HUAWEI P30;HUAWEI P30 Pro. 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-1834/ (Markdown: https://insights.sbomify.com/CVE-2020-1834/index.md)","id":"CVE-2020-1834","markdown":"https://insights.sbomify.com/CVE-2020-1834/index.md","name":"CVE-2020-1834","record":{"aliases":["GHSA-ppg8-7qhw-972w"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone","requires_auth":"none","summary":"Attackers can execute arbitrary code on Huawei P30 devices by loading crafted software packages due to insufficient integrity checks.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p30_firmware","vendor":"huawei"},{"product":"p30_pro_firmware","vendor":"huawei"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"HUAWEI P30 and HUAWEI P30 Pro with versions earlier than 10.1.0.135(C00E135R2P11) and versions earlier than 10.1.0.135(C00E135R2P8) have an insufficient integrity check vulnerability. The system does not check certain software package's integrity sufficiently. Successful exploit could allow an attacker to load a crafted software package to the device.","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":"Code injection in HUAWEI P30;HUAWEI P30 Pro","id":"CVE-2020-1834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in HUAWEI Mate 30","id":"CVE-2020-1835"},"packages":[],"prev":{"headline":"Auth bypass in Honor 9X","id":"CVE-2020-1833"},"products":["HUAWEI P30;HUAWEI P30 Pro"],"published":"2020-06-18","related":[{"cvss_score":7.8,"headline":"Missing authorization in HUAWEI P30","id":"CVE-2020-1800","kev_date_added":null,"published":"2020-03-26"},{"cvss_score":7.8,"headline":"Auth bypass in HUAWEI P30","id":"CVE-2020-1812","kev_date_added":null,"published":"2020-02-18"},{"cvss_score":7.8,"headline":"Integer overflow in P30","id":"CVE-2019-5287","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":7.8,"headline":"Integer overflow in P30","id":"CVE-2019-5288","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":7.5,"headline":"Cross-site scripting in HUAWEI P30","id":"CVE-2021-22331","kev_date_added":null,"published":"2021-04-28"},{"cvss_score":7.5,"headline":"Information disclosure in P30","id":"CVE-2019-5265","kev_date_added":null,"published":"2019-12-23"},{"cvss_score":7.5,"headline":"Denial of service in Share function P30","id":"CVE-2019-5266","kev_date_added":null,"published":"2019-12-23"}],"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 execute arbitrary code on Huawei P30 devices by loading crafted software packages due to insufficient integrity checks.","url":"https://insights.sbomify.com/CVE-2020-1834/"}