# CVE-2014-3224: Denial of service in Quidway S9700,Quidway S9300,Quidway S7700,Quidway S6700,Quidway S6300,Quidway S5700,Quidway S5300 Quidway S9700 V200R003C00SPC500,Quidway S9300 V200R003C00SPC500,Quidway S7700 V200R003C00SPC500,Quidway S6700 V200R003C00SPC300,Quidway S6300 V200R003C00SPC300,Quidway S5700 V200R003C00SPC300,Quidway S5300 V200R003C00SPC300

> Attackers can cause denial of service on Huawei Quidway switches by sending malformed packets, requiring network administrators to apply vendor patches.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7q6p-x5rq-pp4c

## What is CVE-2014-3224?

CVE-2014-3224 is a high-severity denial of service vulnerability in Quidway S9700,Quidway S9300,Quidway S7700,Quidway S6700,Quidway S6300,Quidway S5700,Quidway S5300 Quidway S9700 V200R003C00SPC500,Quidway S9300 V200R003C00SPC500,Quidway S7700 V200R003C00SPC500,Quidway S6700 V200R003C00SPC300,Quidway S6300 V200R003C00SPC300,Quidway S5700 V200R003C00SPC300,Quidway S5300 V200R003C00SPC300, published on 2 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei Quidway S9700 V200R003C00SPC500, Quidway S9300 V200R003C00SPC500, Quidway S7700 V200R003C00SPC500, Quidway S6700 V200R003C00SPC300, Quidway S6300 V200R003C00SPC300, Quidway S5700 V200R003C00SPC300, Quidway S5300 V200R003C00SPC300 enable attackers to launch DoS attacks by crafting and sending malformed packets to these vulnerable products.

Weakness: CWE-399

## Which versions are affected by CVE-2014-3224?

It affects 7 products.


Products: Huawei Quidway S5300 Firmware, Huawei Quidway S5700 Firmware, Huawei Quidway S6300 Firmware, Huawei Quidway S6700 Firmware, Huawei Quidway S7700 Firmware, Huawei Quidway S9300 Firmware, Huawei Quidway S9700 Firmware.

## How do I fix CVE-2014-3224?

No fix has been published for CVE-2014-3224 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-3224 being exploited?

There is no known exploitation of CVE-2014-3224 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3224 and fix it if it is affected.

What it is: CVE-2014-3224 is a high-severity denial of service vulnerability in Quidway S9700,Quidway S9300,Quidway S7700,Quidway S6700,Quidway S6300,Quidway S5700,Quidway S5300 Quidway S9700 V200R003C00SPC500,Quidway S9300 V200R003C00SPC500,Quidway S7700 V200R003C00SPC500,Quidway S6700 V200R003C00SPC300,Quidway S6300 V200R003C00SPC300,Quidway S5700 V200R003C00SPC300,Quidway S5300 V200R003C00SPC300, published on 2 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3224 in the wild and no public exploit code.

Affected product: Quidway S9700,Quidway S9300,Quidway S7700,Quidway S6700,Quidway S6300,Quidway S5700,Quidway S5300 Quidway S9700 V200R003C00SPC500,Quidway S9300 V200R003C00SPC500,Quidway S7700 V200R003C00SPC500,Quidway S6700 V200R003C00SPC300,Quidway S6300 V200R003C00SPC300,Quidway S5700 V200R003C00SPC300,Quidway S5300 V200R003C00SPC300. 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-2014-3224/ (Markdown: https://insights.sbomify.com/CVE-2014-3224/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-3224
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-3224
- OSV: https://osv.dev/vulnerability/CVE-2014-3224

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-3224/
Summaries are generated and may contain mistakes; the official description above is the record.