{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-5228 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5228 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5228 is a high-severity vulnerability in P30, P30 Pro, Honor V20, published on 12 Nov 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-5228 and fix it if it is affected.\n\nWhat it is: CVE-2019-5228 is a high-severity vulnerability in P30, P30 Pro, Honor V20, published on 12 Nov 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-5228 in the wild and no public exploit code.\n\nAffected product: P30, P30 Pro, Honor V20. 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-5228/ (Markdown: https://insights.sbomify.com/CVE-2019-5228/index.md)","id":"CVE-2019-5228","markdown":"https://insights.sbomify.com/CVE-2019-5228/index.md","name":"CVE-2019-5228","record":{"aliases":["GHSA-46rj-wmc7-5p68"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone firmware","requires_auth":"none","summary":"A race condition in Huawei smartphone detection modules allows malicious apps to trigger out-of-bounds writes, leading to arbitrary code execution.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"honor_v20_firmware","vendor":"huawei"},{"product":"p30_firmware","vendor":"huawei"},{"product":"p30_pro_firmware","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Certain detection module of P30, P30 Pro, Honor V20 smartphone whith Versions earlier than ELLE-AL00B 9.1.0.193(C00E190R1P21), Versions earlier than VOGUE-AL00A 9.1.0.193(C00E190R1P12), Versions earlier than Princeton-AL10B 9.1.0.233(C00E233R4P3) have a race condition vulnerability. The system does not lock certain function properly, when the function is called by multiple processes could cause out of bound write. An attacker tricks the user into installing a malicious application, successful exploit could cause malicious 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 P30, P30 Pro, Honor V20","id":"CVE-2019-5228","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":"Missing authorization in P30","id":"CVE-2019-5229"},"packages":[],"prev":{"headline":"Security feature bypass in P30, P30 Pro, Mate 20, HiSuite","id":"CVE-2019-5227"},"products":["P30, P30 Pro, Honor V20"],"published":"2019-11-12","related":[{"cvss_score":5.3,"headline":"Auth bypass in Honor V20","id":"CVE-2020-1803","kev_date_added":null,"published":"2020-04-20"},{"cvss_score":3.3,"headline":"Information disclosure in Honor V20","id":"CVE-2019-5301","kev_date_added":null,"published":"2019-08-08"}],"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 smartphone detection modules allows malicious apps to trigger out-of-bounds writes, leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2019-5228/"}