{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-58313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58313 is a medium-severity vulnerability in Huawei Harmonyos, published on 5 Sep 2025. 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-2025-58313 and fix it if it is affected.\n\nWhat it is: CVE-2025-58313 is a medium-severity vulnerability in Huawei Harmonyos, published on 5 Sep 2025. 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-2025-58313 in the wild and no public exploit code.\n\nAffected product: Huawei Harmonyos. 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-2025-58313/ (Markdown: https://insights.sbomify.com/CVE-2025-58313/index.md)","id":"CVE-2025-58313","markdown":"https://insights.sbomify.com/CVE-2025-58313/index.md","name":"CVE-2025-58313","record":{"aliases":["GHSA-hp73-ggcg-7w7c"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HarmonyOS","requires_auth":"none","summary":"A race condition in the HarmonyOS device standby module can cause feature exceptions, potentially disrupting device functionality.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"harmonyos","vendor":"huawei"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Race condition vulnerability in the device standby module.\nImpact: Successful exploitation of this vulnerability may cause feature exceptions of the device standby module.","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 HarmonyOS","id":"CVE-2025-58313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"huawei:harmonyos","products":["huawei:harmonyos"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in EMUI","id":"CVE-2025-58314"},"packages":[],"prev":{"headline":"Missing authorization in HarmonyOS","id":"CVE-2025-58312"},"products":["HarmonyOS"],"published":"2025-09-05","related":[{"cvss_score":10,"headline":"Memory corruption in HarmonyOS","id":"CVE-2026-34865","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":10,"headline":"Other in HarmonyOS","id":"CVE-2023-34157","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":9.8,"headline":"Denial of service in HarmonyOS","id":"CVE-2023-41294","kev_date_added":null,"published":"2023-09-25"},{"cvss_score":9.8,"headline":"Denial of service in HarmonyOS","id":"CVE-2022-48478","kev_date_added":null,"published":"2023-05-26"},{"cvss_score":9.8,"headline":"Memory corruption in HarmonyOS","id":"CVE-2022-48479","kev_date_added":null,"published":"2023-05-26"},{"cvss_score":9.8,"headline":"Race condition in HarmonyOS","id":"CVE-2022-46316","kev_date_added":null,"published":"2022-12-20"},{"cvss_score":9.8,"headline":"Memory corruption in HarmonyOS","id":"CVE-2022-38980","kev_date_added":null,"published":"2022-10-14"}],"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":"2025-09-05","vendors":["Huawei"]},"summary":"A race condition in the HarmonyOS device standby module can cause feature exceptions, potentially disrupting device functionality.","url":"https://insights.sbomify.com/CVE-2025-58313/"}