{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-5307 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5307 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5307 is a medium-severity vulnerability in Huawei P30,P30 Pro, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-5307 and fix it if it is affected.\n\nWhat it is: CVE-2019-5307 is a medium-severity vulnerability in Huawei P30,P30 Pro, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-5307 in the wild and no public exploit code.\n\nAffected product: Huawei P30,P30 Pro. 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-5307/ (Markdown: https://insights.sbomify.com/CVE-2019-5307/index.md)","id":"CVE-2019-5307","markdown":"https://insights.sbomify.com/CVE-2019-5307/index.md","name":"CVE-2019-5307","record":{"aliases":["GHSA-f9r5-w77x-85qf"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei P30 devices","requires_auth":"none","summary":"Attackers can replay NAS messages via rogue base stations to tamper with GUTIs or obtain IMSIs on Huawei P30 devices.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p30_firmware","vendor":"huawei"},{"product":"p30_pro_firmware","vendor":"huawei"}],"cvss":{"score":4.2,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Some Huawei 4G LTE devices, P30 versions before ELE-AL00 9.1.0.162(C01E160R1P12/C01E160R2P1) and P30 Pro versions before VOG-AL00 9.1.0.162(C01E160R1P12/C01E160R2P1), are exposed to a message replay vulnerability. For the sake of better compatibility, these devices implement a less strict check on the NAS message sequence number (SN), specifically NAS COUNT. As a result, an attacker can construct a rogue base station and replay the GUTI reallocation command message in certain conditions to tamper with GUTIs, or replay the Identity request message to obtain IMSIs. (Vulnerability ID: HWPSIRT-2019-04107)","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":"Other in P30,P30 Pro","id":"CVE-2019-5307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Mate 20 RS","id":"CVE-2019-5308"},"packages":[],"prev":{"headline":"Security feature bypass in P20","id":"CVE-2019-5306"},"products":["P30,P30 Pro"],"published":"2019-06-04","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":["Huawei"]},"summary":"Attackers can replay NAS messages via rogue base stations to tamper with GUTIs or obtain IMSIs on Huawei P30 devices.","url":"https://insights.sbomify.com/CVE-2019-5307/"}