# CVE-2017-2712: Denial of service in S3300

> An attacker can cause Ethernet in the First Mile flapping on Huawei S3300 switches by sending malformed packets, leading to service disruption.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v476-qqh9-vxr9

## What is CVE-2017-2712?

CVE-2017-2712 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S3300, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

S3300 V100R006C05 have an Ethernet in the First Mile (EFM) flapping vulnerability due to the lack of type-length-value (TLV) consistency check. An attacker may craft malformed packets and send them to a device to cause EFM flapping.

Weakness: CWE-417

## Which versions are affected by CVE-2017-2712?

It affects 1 product.


Products: Huawei S3300 Firmware.

## How do I fix CVE-2017-2712?

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

## Is CVE-2017-2712 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2712 and fix it if it is affected.

What it is: CVE-2017-2712 is a medium-severity denial of service vulnerability in Huawei Technologies Co., Ltd. S3300, published on 22 Nov 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-2017-2712 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. S3300. 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-2017-2712/ (Markdown: https://insights.sbomify.com/CVE-2017-2712/index.md)
```

## Sources

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

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