{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-1874 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1874 is a medium-severity vulnerability in Huawei Nip6800 Firmware, published on 28 Feb 2020. 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-2020-1874 and fix it if it is affected.\n\nWhat it is: CVE-2020-1874 is a medium-severity vulnerability in Huawei Nip6800 Firmware, published on 28 Feb 2020. 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-2020-1874 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-1874/ (Markdown: https://insights.sbomify.com/CVE-2020-1874/index.md)","id":"CVE-2020-1874","markdown":"https://insights.sbomify.com/CVE-2020-1874/index.md","name":"CVE-2020-1874","record":{"aliases":["GHSA-vjqf-572p-w4xg"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei network security device","requires_auth":"low_privilege","summary":"An authenticated attacker can cause a process reboot on Huawei network devices by triggering an invalid pointer access during login operations.","user_interaction":"not_required","vuln_class":"null_dereference"},"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.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-824","name":"Access of Uninitialized Pointer"}],"description":"NIP6800;Secospace USG6600;USG9500 products versions of V500R001C30; V500R001C60SPC500; V500R005C00SPC100 have a invalid pointer access vulnerability. The software system access an invalid pointer when operator logs in to the device and performs some operations. Successful exploit could cause certain process reboot.","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":"Null dereference in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1874","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":"null_dereference","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1875"},"packages":[],"prev":{"headline":"Denial of service in NIP6800;Secospace USG6600;USG9500","id":"CVE-2020-1873"},"products":["NIP6800;Secospace USG6600;USG9500"],"published":"2020-02-28","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":["n/a"]},"summary":"An authenticated attacker can cause a process reboot on Huawei network devices by triggering an invalid pointer access during login operations.","url":"https://insights.sbomify.com/CVE-2020-1874/"}