CVE-2017-14329 — Extreme EXOS 16.x, 21.x, and 22.x allows administrators to obtain a root shell via vectors...
Extreme EXOS 16.x, 21.x, and 22.x allows administrators to obtain a root shell via vectors involving an exsh debug shell.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — extremeportal.force.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Extreme Networks Extremexos).
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Extreme Networks | Extremexos |
version 21.1version 22.4version 22.3version 22.2version 22.1version 21.1.4version 21.1.3version 21.1.2 and 9 moreversion 21.1.1version 15.7version 16.2.4version 16.2.3version 16.2.2version 16.2version 16.1.4version 16.1.3version 16.1.2 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.7 | CVSS 3.0 | Medium | 0.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.7 | CVSS 3.0 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.2 | CVSS 2.0 | High | 3.9 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.27%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · extremenetworks/extremexos
- CVSS changed · 6.7
- Source status changed · → Modified
- Record created in this database
- 2017
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 24, 2026 – Oct 24, 2026
- 1× Official description updated · Oct 24, 2026 – Oct 24, 2026
References
3 on the record
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2017-14329 is "Extreme EXOS 16.x, 21.x, and 22.x allows administrators to obtain a root shell via vectors...", rated Medium. It affects Extremexos (Extreme Networks); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.7 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.