{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-48298 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48298 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48298 is a high-severity memory corruption vulnerability in Huawei Emui, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-48298 and fix it if it is affected.\n\nWhat it is: CVE-2022-48298 is a high-severity memory corruption vulnerability in Huawei Emui, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-48298 in the wild and no public exploit code.\n\nAffected product: Huawei Emui. 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-2022-48298/ (Markdown: https://insights.sbomify.com/CVE-2022-48298/index.md)","id":"CVE-2022-48298","markdown":"https://insights.sbomify.com/CVE-2022-48298/index.md","name":"CVE-2022-48298","record":{"aliases":["GHSA-c9q4-2w45-hjcr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei mobile OS","requires_auth":"none","summary":"Attackers can trigger out-of-bounds memory access in the geofencing kernel due to missing input length verification, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"emui","vendor":"huawei"},{"product":"harmonyos","vendor":"huawei"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"The geofencing kernel code does not verify the length of the input data. Successful exploitation of this vulnerability may cause out-of-bounds memory access.","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":"Memory corruption in EMUI","id":"CVE-2022-48298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"huawei:emui","products":["huawei:emui","huawei:harmonyos"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in EMUI","id":"CVE-2022-48299"},"packages":[],"prev":{"headline":"Memory corruption in EMUI","id":"CVE-2022-48297"},"products":["EMUI","HarmonyOS"],"published":"2023-02-09","related":[{"cvss_score":9.8,"headline":"Memory corruption in EMUI","id":"CVE-2023-52370","kev_date_added":null,"published":"2024-02-18"},{"cvss_score":9.8,"headline":"Business logic in EMUI","id":"CVE-2023-52378","kev_date_added":null,"published":"2024-02-18"},{"cvss_score":9.8,"headline":"Code injection in EMUI","id":"CVE-2023-52381","kev_date_added":null,"published":"2024-02-18"},{"cvss_score":9.8,"headline":"Memory corruption in EMUI","id":"CVE-2023-52103","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":9.8,"headline":"Privilege escalation in EMUI","id":"CVE-2023-46773","kev_date_added":null,"published":"2023-12-06"},{"cvss_score":9.8,"headline":"Privilege escalation in EMUI","id":"CVE-2023-44105","kev_date_added":null,"published":"2023-10-11"},{"cvss_score":9.8,"headline":"Privilege escalation in EMUI","id":"CVE-2023-44106","kev_date_added":null,"published":"2023-10-11"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["Huawei"]},"summary":"Attackers can trigger out-of-bounds memory access in the geofencing kernel due to missing input length verification, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2022-48298/"}