CVE-2021-34699
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 · uneditedA vulnerability in the TrustSec CLI parser of Cisco IOS and Cisco IOS XE Software could allow an authenticated, remote attacker to cause an affected device to reload. This vulnerability is due to an improper interaction between the web UI and the CLI parser. An attacker could exploit this vulnerability by requesting a particular CLI command to be run through the web UI. A successful exploit could allow the attacker to cause the device to reload, resulting in a denial of service (DoS) condition.
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 · high confidenceA vulnerability in the TrustSec CLI parser of Cisco IOS and Cisco IOS XE Software allows an authenticated, remote attacker to cause device reload by requesting a specific CLI command through the web UI. The root cause is improper interaction between the web UI and CLI parser, leading to a denial of service condition.
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= 12.2\(6\)i1= 15.0\(1\)sy= 15.0\(1\)sy1= 15.0\(1\)sy2= 15.0\(1\)sy3= 15.0\(1\)sy4= 15.0\(1\)sy5= 15.0\(1\)sy6= 15.0\(1\)sy7= 15.0\(1\)sy7a= 15.0\(1\)sy8= 15.0\(1\)sy9= 3.3.0se= 3.3.0xo= 3.3.1se= 3.3.1xo= 3.3.2se= 3.3.2xo= 3.3.3se= 3.3.4se= 3.3.5se= 3.5.0e= 3.5.1e= 3.5.2eCVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 device OS and versionExecute `show version` on the device CLI to display the running IOS or IOS XE versionAffected if The displayed version matches one of the vulnerable versions: Cisco iOS 12.2(6)i1, 15.0(1)sy through 15.0(1)sy9; Cisco IOS XE 3.3.0se through 3.5.2e
-
Verify web UI is enabledRun `show running-config | include ip http server|secure-server` or check configuration for `ip http server` or `ip secure http server`Affected if HTTP or HTTPS server is enabled (the attack exploits the web UI interface to trigger the vulnerable CLI parser)
-
Confirm TrustSec is licensed or availableCheck `show version | include TrustSec` or verify the device model supports TrustSec featuresAffected if The device has TrustSec capability (the vulnerability exists in the TrustSec CLI parser component)
-
Check for recent reload eventsReview `show reload` history and `show log` for unexpected reloads, particularly those without clear causeAffected if Device has experienced unexplained reloads that could indicate exploitation attempts
Device is affected if it runs a vulnerable IOS or IOS XE version AND has the web UI enabled, as the attacker exploits the web UI to trigger the TrustSec CLI parser vulnerability causing device reload.
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.
dbcve · scopedApply the relevant Cisco security update for CVE-2021-34699 to affected IOS/IOS XE devices. If patching is not immediately possible, consider disabling the web UI or restricting web UI access to trusted sources only.
Cisco IOS 15.5(3)M or later / Cisco IOS XE 16.9.1 or later (specific to your platform - consult Cisco advisory)
- 1. Identify the exact Cisco IOS or IOS XE version currently running on the affected device using the 'show version' command.
- 2. Access Cisco's official security advisory for CVE-2021-34699 at tools.cisco.com to obtain the specific fixed release for your product line.
- 3. Download the appropriate fixed IOS or IOS XE software release from Cisco's software download center.
- 4. Plan an upgrade window as the device will need to be reloaded during the upgrade process.
- 5. Back up the current device configuration before proceeding with the upgrade.
- 6. Upload the new software image to the device using TFTP, FTP, or USB transfer methods.
- 7. Configure the device to boot from the new image using the 'boot system' command.
- 8. Reload the device with the 'reload' command to apply the new software version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34699 — 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-2021-34699 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