{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-1814 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1814 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1814 is a medium-severity vulnerability in Huawei Nip6800 Firmware, published on 18 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1814 and fix it if it is affected.\n\nWhat it is: CVE-2020-1814 is a medium-severity vulnerability in Huawei Nip6800 Firmware, published on 18 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-1814 in the wild and no public exploit code.\n\nAffected product: Huawei Nip6800 Firmware. 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-2020-1814/ (Markdown: https://insights.sbomify.com/CVE-2020-1814/index.md)","id":"CVE-2020-1814","markdown":"https://insights.sbomify.com/CVE-2020-1814/index.md","name":"CVE-2020-1814","record":{"aliases":["GHSA-gvmv-7rg8-v686"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei network security device","requires_auth":"low_privilege","summary":"An authenticated attacker can trigger a race condition leading to a dangling pointer dereference, causing service disruption on Huawei network security devices.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"nip6800_firmware","vendor":"huawei"},{"product":"secospace_usg6600_firmware","vendor":"huawei"},{"product":"usg9500_firmware","vendor":"huawei"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:L/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"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have a Dangling pointer dereference vulnerability. An authenticated attacker may do some special operations in the affected products in some special scenarios to exploit the vulnerability. Due to improper race conditions of different operations, successful exploit will lead to Dangling pointer dereference, causing some service abnormal.","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 NIP6800","id":"CVE-2020-1814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"huawei:nip6800_firmware","products":["huawei:nip6800_firmware","huawei:secospace_usg6600_firmware","huawei:usg9500_firmware"],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in NIP6800","id":"CVE-2020-1815"},"packages":[],"prev":{"headline":"Auth bypass in HUAWEI P30","id":"CVE-2020-1813"},"products":["NIP6800","Secospace USG6600, USG9500"],"published":"2020-02-18","related":[{"cvss_score":7.5,"headline":"Auth bypass in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1860","kev_date_added":null,"published":"2020-02-28"},{"cvss_score":7.5,"headline":"Denial of service in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1873","kev_date_added":null,"published":"2020-02-28"},{"cvss_score":7.5,"headline":"Memory corruption in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1876","kev_date_added":null,"published":"2020-02-28"},{"cvss_score":7.5,"headline":"Denial of service in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1881","kev_date_added":null,"published":"2020-02-28"},{"cvss_score":7.5,"headline":"Denial of service in NIP6800","id":"CVE-2020-1815","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":7.5,"headline":"Denial of service in NIP6800","id":"CVE-2020-1816","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":7.5,"headline":"Information disclosure in NIP6800","id":"CVE-2020-1827","kev_date_added":null,"published":"2020-02-17"}],"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":"An authenticated attacker can trigger a race condition leading to a dangling pointer dereference, causing service disruption on Huawei network security devices.","url":"https://insights.sbomify.com/CVE-2020-1814/"}