CVE-2014-3223
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 · uneditedHuawei S9300 with software before V100R006SPH013 and S2300,S3300,S5300,S6300 with software before V100R006SPH010 support Y.1731 and therefore have the Y.1731 vulnerability in processing special packets. The vulnerability causes the restart of switches.
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 confidenceHuawei S9300, S2300, S3300, S5300, and S6300 switches contain a denial-of-service vulnerability in the Y.1731 (Ethernet OAM) protocol implementation. Specially crafted Y.1731 packets trigger a fault during packet processing that causes the affected switch to restart, resulting in service disruption.
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= v100r006c00spc500= v100r006c00spc800= v100r006c00spc800= v100r006c01spc100= v100r006c03= v100r006c00spc800= v100r006c01spc100= v100r006c03= v100r006c00spc800= v100r006c01spc100= v100r006c03= v100r006c00spc800= v100r006c01spc100= v100r006c03CVSS 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
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the switch modelRun the command `display device` or `display version` on the switch CLI to determine if the device is an S9300, S2300, S3300, S5300, or S6300 model.Affected if The model is one of these five series.
-
Check the installed firmware versionRun `display version` and locate the Software Version field. Compare it against the affected version list: S9300 (v100r006c00spc500, v100r006c00spc800), S3300/S2300/S5300/S6300 (v100r006c00spc800, v100r006c01spc100, v100r006c03).Affected if The firmware version exactly matches one of the listed affected versions.
-
Verify if Y.1731 protocol is enabledRun `display current-configuration | include y1731` or `display ethernet oam configuration` to check for Y.1731 or Ethernet OAM configuration in the active running configuration.Affected if Y.1731 or Ethernet OAM functionality is configured and enabled on any interface.
-
Check for Y.1731 related processes or featuresRun `display feature` or `display current-configuration | include feature` to see if the Ethernet OAM feature is activated on the device.Affected if The Ethernet OAM or Y.1731 feature is in the active feature list.
The device is affected if it is an S9300/S2300/S3300/S5300/S6300 switch running one of the specific affected firmware versions AND has Y.1731/Ethernet OAM protocol enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Huawei S9300 to V100R006SPH013 or later, and S2300/S3300/S5300/S6300 to V100R006SPH010 or later. If immediate patching is not feasible, evaluate disabling Y.1731 or implementing network access controls to limit exposure to untrusted network segments.
- Consultation5.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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