{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-5216 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5216 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5216 is a high-severity vulnerability in Huawei Honor V10, Honor 10, Honor Play, published on 6 Jun 2019. 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-2019-5216 and fix it if it is affected.\n\nWhat it is: CVE-2019-5216 is a high-severity vulnerability in Huawei Honor V10, Honor 10, Honor Play, published on 6 Jun 2019. 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-2019-5216 in the wild and no public exploit code.\n\nAffected product: Huawei Honor V10, Honor 10, Honor Play. 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-2019-5216/ (Markdown: https://insights.sbomify.com/CVE-2019-5216/index.md)","id":"CVE-2019-5216","markdown":"https://insights.sbomify.com/CVE-2019-5216/index.md","name":"CVE-2019-5216","record":{"aliases":["GHSA-657p-ghh6-v8fr"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Honor smartphone","requires_auth":"none","summary":"A race condition in Huawei Honor smartphones allows malicious apps to execute arbitrary code by manipulating shared variables.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_10_firmware","vendor":"huawei"},{"product":"honor_play_firmware","vendor":"huawei"},{"product":"honor_view_10_firmware","vendor":"huawei"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"There is a race condition vulnerability on Huawei Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.156(C00E156R2P14T8), Honor 10 smartphones versions earlier than Columbia-AL10B 9.0.0.156(C00E156R1P20T8) and Honor Play smartphones versions earlier than Cornell-AL00A 9.0.0.156(C00E156R1P13T8). An attacker tricks the user into installing a malicious application, which makes multiple processes to operate the same variate at the same time. Successful exploit could cause execution of malicious code.","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 Honor V10, Honor 10, Honor Play","id":"CVE-2019-5216","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Mate 9 Pro","id":"CVE-2019-5217"},"packages":[],"prev":{"headline":"Other in P30,P30 Pro","id":"CVE-2019-5215"},"products":["Honor V10, Honor 10, Honor Play"],"published":"2019-06-06","related":[{"cvss_score":5.5,"headline":"Denial of service in Honor 10","id":"CVE-2020-9255","kev_date_added":null,"published":"2020-07-17"},{"cvss_score":5.5,"headline":"Denial of service in Mate 10 Pro;Honor V10;Honor 10;Nova 4","id":"CVE-2020-1785","kev_date_added":null,"published":"2020-01-03"}],"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":"A race condition in Huawei Honor smartphones allows malicious apps to execute arbitrary code by manipulating shared variables.","url":"https://insights.sbomify.com/CVE-2019-5216/"}