iOSOperating system · Cisco
CVE-2018-0282
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 TCP socket code of Cisco IOS and IOS XE Software could allow an unauthenticated, remote attacker to cause an affected device to reload. The vulnerability is due to a state condition between the socket state and the transmission control block (TCB) state. While this vulnerability potentially affects all TCP applications, the only affected application observed so far is the HTTP server. An attacker could exploit this vulnerability by sending specific HTTP requests at a sustained rate to a reachable IP address of the affected software. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a denial of service (DoS) condition on an affected device.
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 confidenceCVE-2018-0282 is a vulnerability in the TCP socket code of Cisco IOS and IOS XE Software caused by a state condition mismatch between socket state and the Transmission Control Block (TCB). While potentially affecting all TCP applications, the HTTP server is the only observed affected application. An unauthenticated remote attacker can exploit this by sending specific HTTP requests at a sustained rate to a reachable IP address, causing the affected device to reload 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
iOSOperating system
= 15.2\(2\)e4
Ios XeOperating system
all versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 the Cisco IOS or IOS XE versionExecute 'show version' on the device CLI and locate the software version string in the output (e.g., 'Version 15.2(2)E4' or IOS XE version number)Affected if The version matches 15.2(2)e4 for Cisco iOS, or any version for Cisco IOS XE (all versions affected)
-
Confirm HTTP server is enabledExecute 'show ip http server status' or 'show running-config | include ip http server' to check if the HTTP server feature is activeAffected if HTTP server is enabled (the vulnerability only manifests through the HTTP server)
-
Verify HTTP server is network reachableFrom an external host, attempt to reach the device HTTP port (TCP 80) or verify ACLs and interface configurations allow HTTP accessAffected if The HTTP server is reachable from untrusted networks - an attacker must be able to send sustained HTTP requests to the device
You are affected if your device runs Cisco iOS version 15.2(2)e4 or any Cisco IOS XE version, has the HTTP server enabled, and the HTTP service is network-accessible to an attacker.
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 dataApply the relevant Cisco IOS/IOS XE software updates when available; in the interim, consider implementing rate limiting or access controls on the HTTP server to limit sustained request attacks.
Fix this in iOS
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0282 — 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-2018-0282 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