{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-48613 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48613 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48613 is a medium-severity vulnerability in Huawei Emui, published on 8 Nov 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-48613 and fix it if it is affected.\n\nWhat it is: CVE-2022-48613 is a medium-severity vulnerability in Huawei Emui, published on 8 Nov 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-48613 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-48613/ (Markdown: https://insights.sbomify.com/CVE-2022-48613/index.md)","id":"CVE-2022-48613","markdown":"https://insights.sbomify.com/CVE-2022-48613/index.md","name":"CVE-2022-48613","record":{"aliases":["GHSA-5q3h-x43w-q8hj"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei mobile OS","requires_auth":"none","summary":"A race condition in the kernel module allows attackers to bypass condition evaluations and read variable values.","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":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Race condition vulnerability in the kernel module. Successful exploitation of this vulnerability may cause variable values to be read with the condition evaluation bypassed.","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-48613","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":"Cross-site Scripting in Semantic MediaWiki","id":"CVE-2022-48614"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-48612"},"products":["EMUI","HarmonyOS"],"published":"2023-11-08","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["Huawei"]},"summary":"A race condition in the kernel module allows attackers to bypass condition evaluations and read variable values.","url":"https://insights.sbomify.com/CVE-2022-48613/"}