{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1839 is a medium-severity vulnerability in HUAWEI Mate 30, published on 6 Jul 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-1839 and fix it if it is affected.\n\nWhat it is: CVE-2020-1839 is a medium-severity vulnerability in HUAWEI Mate 30, published on 6 Jul 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-1839 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-1839/ (Markdown: https://insights.sbomify.com/CVE-2020-1839/index.md)","id":"CVE-2020-1839","markdown":"https://insights.sbomify.com/CVE-2020-1839/index.md","name":"CVE-2020-1839","record":{"aliases":["GHSA-7qcq-7635-mr77"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HUAWEI Mate 30","requires_auth":"high_privilege","summary":"A race condition in HUAWEI Mate 30 allows attackers to execute arbitrary code by tricking users into running a crafted high-privilege application.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"mate_30_firmware","vendor":"huawei"}],"cvss":{"score":6.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"HUAWEI Mate 30 with versions earlier than 10.1.0.150(C00E136R5P3) have a race condition vulnerability. There is a timing window exists in which certain pointer members can be modified by another process that is operating concurrently, an attacker should trick the user into running a crafted application with high privilege, successful exploit could cause code execution.","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":"Race condition in HUAWEI Mate 30","id":"CVE-2020-1839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in HUAWEI Mate 20","id":"CVE-2020-1840"},"packages":[],"prev":{"headline":"Auth bypass in HUAWEI Mate 30 Pro","id":"CVE-2020-1838"},"products":["HUAWEI Mate 30"],"published":"2020-07-06","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"},{"cvss_score":6.5,"headline":"Information disclosure in HUAWEI Mate 30","id":"CVE-2020-1835","kev_date_added":null,"published":"2020-06-18"}],"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":"A race condition in HUAWEI Mate 30 allows attackers to execute arbitrary code by tricking users into running a crafted high-privilege application.","url":"https://insights.sbomify.com/CVE-2020-1839/"}