{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2019-5227 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5227 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5227 is a medium-severity vulnerability in P30, P30 Pro, Mate 20, HiSuite, published on 29 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-5227 and fix it if it is affected.\n\nWhat it is: CVE-2019-5227 is a medium-severity vulnerability in P30, P30 Pro, Mate 20, HiSuite, published on 29 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-5227 in the wild and no public exploit code.\n\nAffected product: P30, P30 Pro, Mate 20, HiSuite. 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-5227/ (Markdown: https://insights.sbomify.com/CVE-2019-5227/index.md)","id":"CVE-2019-5227","markdown":"https://insights.sbomify.com/CVE-2019-5227/index.md","name":"CVE-2019-5227","record":{"aliases":["GHSA-qr6w-xx8m-93mv"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei HiSuite","requires_auth":"none","summary":"Attackers can downgrade Huawei smartphones to vulnerable older versions by bypassing insufficient validation in HiSuite upgrade packages.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"hisuite_firmware","vendor":"huawei"},{"product":"mate_20_firmware","vendor":"huawei"},{"product":"p30_firmware","vendor":"huawei"},{"product":"p30_pro_firmware","vendor":"huawei"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"P30, P30 Pro, Mate 20 smartphones with software of versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1), versions earlier than VOGUE-AL00A 9.1.0.193(C00E190R2P1), versions earlier than Hima-AL00B 9.1.0.135(C00E133R2P1) and HiSuite with versions earlier than HiSuite 9.1.0.305 have a version downgrade vulnerability. The device and HiSuite software do not validate the upgrade package sufficiently, so that the system of smartphone can be downgraded to an older version.","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":"Security feature bypass in P30, P30 Pro, Mate 20, HiSuite","id":"CVE-2019-5227","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in P30, P30 Pro, Honor V20","id":"CVE-2019-5228"},"packages":[],"prev":{"headline":"Security feature bypass in P30, P30 Pro, Mate 20, HiSuite","id":"CVE-2019-5226"},"products":["P30, P30 Pro, Mate 20, HiSuite"],"published":"2019-11-29","related":[{"cvss_score":5.5,"headline":"Security feature bypass in P30, P30 Pro, Mate 20, HiSuite","id":"CVE-2019-5226","kev_date_added":null,"published":"2019-11-29"}],"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 downgrade Huawei smartphones to vulnerable older versions by bypassing insufficient validation in HiSuite upgrade packages.","url":"https://insights.sbomify.com/CVE-2019-5227/"}