CVE-2017-14328
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 · uneditedExtreme EXOS 15.7, 16.x, 21.x, and 22.x allows remote attackers to trigger a buffer overflow leading to a reboot.
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 confidenceA buffer overflow vulnerability in Extreme Networks EXOS firmware versions 15.7, 16.x, 21.x, and 22.x allows remote, unauthenticated attackers to trigger the overflow, causing a device reboot (denial of service). The vulnerability is network-exploitable with CVSS 7.5 indicating high availability impact.
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= 15.7= 16.1= 16.1.2= 16.1.3= 16.1.4= 16.1.5= 16.2= 16.2.2= 16.2.3= 16.2.4= 16.2.5= 21.1CVSS 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.1/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 EXOS device and modelLog into the Extreme Networks switch or Summit device and run 'show version' or 'show switch' command to identify the hardware model and EXOS software versionAffected if The displayed EXOS version matches 15.7, 16.1.x, 16.2.x, 21.1.x, or 22.x (any version in the 15.7 through 22.x range)
-
Verify EXOS version numberFrom the 'show version' output, locate the EXOS software version string (typically shown as 'EXOS version 15.7.x.x' or similar)Affected if The exact version string corresponds to any of the affected versions listed: 15.7, 16.1, 16.1.2, 16.1.3, 16.1.4, 16.1.5, 16.2, 16.2.2, 16.2.3, 16.2.4, 16.2.5, or 21.1 (or falls within 21.x or 22.x range)
-
Confirm management interface exposureReview network configuration using 'show ip management' or check ACL definitions with 'show access-list' to determine if the management interface (telnet, HTTP, HTTPS, or SNMP) is reachable from untrusted networksAffected if Management interfaces are accessible from network segments outside the trusted management VLAN, indicating the device is network-exploitable without additional network restrictions
The device is affected if it runs EXOS firmware versions 15.7 through 22.x (specifically the listed versions) and has management interfaces exposed to untrusted networks, allowing remote unauthenticated attackers to trigger the buffer overflow and cause denial of service.
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 EXOS firmware to a version beyond 22.x that includes the security patch. If immediate patching is not feasible, restrict network access to management interfaces using ACLs or VPN tunnels to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14328 — 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-2017-14328 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