dbcve.org
S3300 FirmwareOperating system · Huawei

CVE-2017-2712

MEDIUM · 5.3 CVSS v3.0 Published 2017-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Huawei S3300 V100R006C05 switch has a vulnerability in its Ethernet in the First Mile (EFM) protocol implementation. The device lacks proper type-length-value (TLV) consistency validation when processing EFM packets. An attacker can send crafted malformed packets to trigger EFP flapping, causing service disruption through repeated protocol state changes.

MitigationApply the vendor patch from Huawei for V100R006C05. Until patched, consider network segmentation or ACL filtering to limit exposure to untrusted network segments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
S3300 FirmwareOperating system
Affected:= v100r006c05

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Display the device system information using 'display device' or 'display version' command to confirm the hardware is Huawei S3300
    Affected if Device model is not Huawei S3300, then not affected by this specific CVE
  2. Check the firmware version
    Execute 'display version' or 'display bootrom' command to retrieve the current software version running on the S3300 switch
    Affected if Firmware version is exactly V100R006C05 - other versions are not affected by this specific CVE
  3. Verify EFM protocol status
    Run 'display efm interface' or 'display efm configuration' to check if Ethernet in the First Mile (EFM) protocol is enabled on any interface
    Affected if EFM protocol is actively enabled on one or more interfaces - this is required for the vulnerability to be exploitable
  4. Inspect EFM TLV configuration
    Use 'display efm interface' or examine the EFM packet handling settings to see if TLV validation is configured
    Affected if EFM is enabled with default or minimal TLV validation settings - lack of proper TLV consistency validation is the vulnerable condition

Affected if running Huawei S3300 with firmware V100R006C05 AND EFM protocol is enabled on at least one interface, making it susceptible to malformed EFM packet injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Huawei for V100R006C05. Until patched, consider network segmentation or ACL filtering to limit exposure to untrusted network segments.

Fix this in S3300 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data