{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-48357 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48357 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48357 is a high-severity vulnerability in Huawei Emui, published on 27 Mar 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-48357 and fix it if it is affected.\n\nWhat it is: CVE-2022-48357 is a high-severity vulnerability in Huawei Emui, published on 27 Mar 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-48357 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-48357/ (Markdown: https://insights.sbomify.com/CVE-2022-48357/index.md)","id":"CVE-2022-48357","markdown":"https://insights.sbomify.com/CVE-2022-48357/index.md","name":"CVE-2022-48357","record":{"aliases":["GHSA-998w-8vh9-h5jv"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei mobile OS","requires_auth":"none","summary":"A double fetch race condition in Huawei EMUI and HarmonyOS kernels allows attackers to cause a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Some products have the double fetch vulnerability. Successful exploitation of this vulnerability may cause denial of service (DoS) attacks to the kernel.","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 EMUI","id":"CVE-2022-48357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"huawei:emui","products":["huawei:emui","huawei:harmonyos"],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Open redirect in EMUI","id":"CVE-2022-48358"},"packages":[],"prev":{"headline":"Other in EMUI","id":"CVE-2022-48356"},"products":["EMUI","HarmonyOS"],"published":"2023-03-27","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-02-19","vendors":["Huawei"]},"summary":"A double fetch race condition in Huawei EMUI and HarmonyOS kernels allows attackers to cause a denial of service.","url":"https://insights.sbomify.com/CVE-2022-48357/"}