Ios XeOperating system · Cisco
CVE-2015-0688
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 · uneditedCisco IOS XE 3.10.2S on an ASR 1000 device with an Embedded Services Processor (ESP) module, when NAT is enabled, allows remote attackers to cause a denial of service (module crash) via malformed H.323 packets, aka Bug ID CSCup21070.
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 denial of service vulnerability in Cisco IOS XE 3.10.2S on ASR 1000 devices with an Embedded Services Processor (ESP) module allows remote attackers to crash the ESP module by sending malformed H.323 packets when NAT is enabled.
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
Ios XeOperating system
= 13.10.2sCVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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.
-
Confirm ASR 1000 series hardwareExecute 'show version' or 'show inventory' to verify the device model is Cisco ASR 1000 seriesAffected if Device is not an ASR 1000 series router - this vulnerability only affects ASR 1000 platforms
-
Verify IOS XE version 3.10.2SRun 'show version' and locate the IOS XE release string. Confirm it shows exactly 3.10.2S (the '=' notation in the advisory indicates this specific version)Affected if IOS XE version is not 3.10.2S - only this exact version is affected
-
Confirm ESP module is present and activeRun 'show module' or 'show hardware' to verify an Embedded Services Processor module is installed and in 'Up' stateAffected if No ESP module is present or it is not operational - the vulnerability requires an active ESP
-
Check if NAT is enabledRun 'show ip nat translations' or 'show running-config | include nat' to determine if Network Address Translation is configured and activeAffected if NAT is not enabled - the flaw only triggers when NAT is active on the device
-
Determine if H.323 traffic can reach the deviceReview access-logs, firewall rules, or run 'show connection' to assess whether H.323 traffic from external sources could be received on WAN/public-facing interfacesAffected if H.323 traffic cannot reach the device - the malformed packets must be received to trigger the crash
User is affected only if: device is ASR 1000, running IOS XE exactly 3.10.2S, has an active ESP module, NAT is enabled, and malformed H.323 packets can reach the device from the network.
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 Cisco IOS XE to a patched version; alternatively, filter or block malformed H.323 traffic at the network perimeter until the upgrade can be applied.
Fix this in Ios Xe
Scoped from the published advisory
- 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-2015-0688 — 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-2015-0688 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