CVE-2021-1460
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 Cisco IOx Application Framework of Cisco 809 Industrial Integrated Services Routers (Industrial ISRs), Cisco 829 Industrial ISRs, Cisco CGR 1000 Compute Module, and Cisco IC3000 Industrial Compute Gateway could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient error handling during packet processing. An attacker could exploit this vulnerability by sending a high and sustained rate of crafted TCP traffic to the IOx web server on an affected device. A successful exploit could allow the attacker to cause the IOx web server to stop processing requests, resulting in a 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 confidenceThis vulnerability exists in the Cisco IOx Application Framework's web server component on affected Industrial ISR and Compute Gateway devices. An unauthenticated remote attacker can exploit insufficient error handling during packet processing by sending a high, sustained rate of crafted TCP traffic to the IOx web server, causing it to stop processing requests and resulting in denial of service.
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.9\(3\)m3< 1.12.0.3< 1.3.2CVSS 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 device modelDetermine if the device is an Industrial ISR, CGR1000, or IC3000 Industrial Compute Gateway using 'show version' or physical labelingAffected if Device model is not one of these three affected product lines - not vulnerable
-
Verify IOx is enabledCheck if IOx application hosting feature is enabled on the device using 'show iox' commandAffected if IOx is not installed or not enabled - not vulnerable
-
Check iOS version (for Industrial ISR)Run 'show version' and check the iOS version. Look for versions < 15.9(3)m3Affected if iOS version is 15.9(3)m3 or higher - not vulnerable (note: format may vary, compare numerically)
-
Check CGR1000 firmware versionFor CGR1000 devices, check firmware version using 'show hardware' or 'show version' and verify it is < 1.12.0.3Affected if Firmware version is 1.12.0.3 or higher - not vulnerable
-
Check IC3000 firmware versionFor IC3000 Industrial Compute Gateway, check firmware version and verify it is < 1.3.2Affected if Firmware version is 1.3.2 or higher - not vulnerable
-
Assess network exposure of IOx web serverVerify if IOx web server ports (default 443/8443) are exposed to untrusted networks using 'show ip interface' or network scansAffected if IOx web server is only accessible from trusted networks - reduced exposure, though the vulnerability still exists if versions are affected
Device is affected if it is a Cisco Industrial ISR, CGR1000, or IC3000 with IOx enabled AND the installed version/firmware is below the affected thresholds listed.
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 data1.3.21.12.0.315.9
Apply the Cisco vendor patch when available. In the interim, implement network-level controls such as firewall rules or ACLs to restrict access to the IOx web server ports from untrusted networks, and consider rate limiting on perimeter devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1460 — 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-1460 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