{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-1827 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1827 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1827 is a high-severity vulnerability in Huawei Nip6800 Firmware, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1827 and fix it if it is affected.\n\nWhat it is: CVE-2020-1827 is a high-severity vulnerability in Huawei Nip6800 Firmware, published on 17 Feb 2020. 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-2020-1827 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-1827/ (Markdown: https://insights.sbomify.com/CVE-2020-1827/index.md)","id":"CVE-2020-1827","markdown":"https://insights.sbomify.com/CVE-2020-1827/index.md","name":"CVE-2020-1827","record":{"aliases":["GHSA-r895-r5c8-hvhp"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei network security device","requires_auth":"none","summary":"An attacker can send specific request packets to Huawei NIP and Secospace devices to leak sensitive information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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":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-404","name":"Improper Resource Shutdown or Release"}],"description":"Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00SPC100; and Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100 have an information leakage vulnerability. An attacker can exploit this vulnerability by sending specific request packets to affected devices. Successful exploit may lead to information leakage.","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":"Information disclosure in NIP6800","id":"CVE-2020-1827","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":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in NIP6800","id":"CVE-2020-1828"},"packages":[],"prev":{"headline":"Weak cryptography in Honor Magic2","id":"CVE-2020-1826"},"products":["NIP6800","Secospace USG6600, USG9500"],"published":"2020-02-17","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"}],"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 attacker can send specific request packets to Huawei NIP and Secospace devices to leak sensitive information.","url":"https://insights.sbomify.com/CVE-2020-1827/"}