{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5224 is a medium-severity vulnerability in P30, 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-5224 and fix it if it is affected.\n\nWhat it is: CVE-2019-5224 is a medium-severity vulnerability in P30, 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-5224 in the wild and no public exploit code.\n\nAffected product: P30. 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-5224/ (Markdown: https://insights.sbomify.com/CVE-2019-5224/index.md)","id":"CVE-2019-5224","markdown":"https://insights.sbomify.com/CVE-2019-5224/index.md","name":"CVE-2019-5224","record":{"aliases":["GHSA-vr74-fpq9-774p"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei P30 smartphone","requires_auth":"none","summary":"A malicious application can trigger an out-of-bounds read in the kernel, leading to information disclosure on Huawei P30 devices.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p30_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:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"P30 smartphones with versions earlier than ELLE-AL00B 9.1.0.193(C00E190R1P21) have an out of bounds read vulnerability. The system does not properly validate certain length parameter which an application transports to kernel. An attacker tricks the user to install a malicious application, successful exploit could cause out of bounds read and information disclosure.","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":"Information disclosure in P30","id":"CVE-2019-5224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in P30, Mate 20, P30 Pro","id":"CVE-2019-5225"},"packages":[],"prev":{"headline":"Auth bypass in PC Manager","id":"CVE-2019-5223"},"products":["P30"],"published":"2019-11-29","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":"A malicious application can trigger an out-of-bounds read in the kernel, leading to information disclosure on Huawei P30 devices.","url":"https://insights.sbomify.com/CVE-2019-5224/"}