# CVE-2019-5255: Denial of service in AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981 > Attackers can cause denial of service on Huawei network devices by sending crafted FTP messages that trigger an out-of-bounds read. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 13 Dec 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-64cp-w546-6qxq ## What is CVE-2019-5255? CVE-2019-5255 is a medium-severity denial of service vulnerability in Huawei Nip6300 Firmware, published on 13 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have a DoS vulnerability. An attacker may send crafted messages from a FTP client to exploit this vulnerability. Due to insufficient validation of the message, successful exploit may cause the system out-of-bounds read and result in a denial of service condition of the affected service. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2019-5255? It affects 17 products. Products: Huawei Ap2000 Firmware, Huawei Espace U1981 Firmware, Huawei Ips Firmware, Huawei Ngfw Firmware, Huawei Nip6300 Firmware, Huawei Nip6600 Firmware, Huawei Nip6800 Firmware, Huawei S5700 Firmware, Huawei Secospace Antiddos8000 Firmware, Huawei Secospace Usg6300 Firmware, Huawei Secospace Usg6500 Firmware, Huawei Secospace Usg6600 Firmware, Huawei Semg9811 Firmware, Huawei Svn5600 Firmware, Huawei Svn5800-C Firmware, Huawei Svn5800 Firmware, Huawei Usg6000v Firmware. ## How do I fix CVE-2019-5255? No fix has been published for CVE-2019-5255 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-5255 being exploited? There is no known exploitation of CVE-2019-5255 in the wild and no public exploit code. ## Other vulnerabilities in Huawei Nip6300 Firmware - [CVE-2019-5254](https://insights.sbomify.com/CVE-2019-5254/): Memory corruption in AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981 (high 8.6) - [CVE-2019-5256](https://insights.sbomify.com/CVE-2019-5256/): Null dereference in AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981 (medium 5.5) - [CVE-2019-5257](https://insights.sbomify.com/CVE-2019-5257/): Denial of service in AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981 (medium 5.5) - [CVE-2019-5258](https://insights.sbomify.com/CVE-2019-5258/): Memory corruption in AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981 (medium 5.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-5255 and fix it if it is affected. What it is: CVE-2019-5255 is a medium-severity denial of service vulnerability in Huawei Nip6300 Firmware, published on 13 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-5255 in the wild and no public exploit code. Affected product: Huawei Nip6300 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-5255/ (Markdown: https://insights.sbomify.com/CVE-2019-5255/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5255 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5255 - OSV: https://osv.dev/vulnerability/CVE-2019-5255 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-5255/ Summaries are generated and may contain mistakes; the official description above is the record.