iOSOperating system · Cisco
CVE-2013-1144
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 · uneditedMemory leak in the IKEv1 implementation in Cisco IOS 15.1 allows remote attackers to cause a denial of service (memory consumption) via unspecified (1) IPv4 or (2) IPv6 IKE packets, aka Bug ID CSCth81055.
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 confidenceMemory leak in Cisco IOS 15.1's IKEv1 (Internet Key Exchange version 1) implementation allows remote attackers to cause denial of service by sending specially crafted IKE packets over IPv4 or IPv6. The vulnerability leads to uncontrolled memory consumption, eventually exhausting device resources and causing the system to become unavailable.
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.1CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/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.
-
Check Cisco IOS versionRun 'show version' on the device and locate the IOS version number in the outputAffected if The version shown is exactly 15.1 (e.g., 15.1, 15.1(1)T, 15.1.1, etc.)
-
Verify IKEv1 is configuredRun 'show crypto isakmp policy' or 'show running-config | include isakmp' to see if any IKEv1 policies existAffected if Any IKEv1 (ISAKMP) policy configuration is present on the device
-
Confirm IKEv1 enablement statusRun 'show crypto isakmp sa' to check for active IKEv1 security associations, and check interface configs for 'crypto map' applied to interfacesAffected if IKEv1 is actively enabled via crypto maps applied to interfaces
-
Check IPv4/IPv6 exposureVerify if the device has IPv4 or IPv6 addresses on interfaces with crypto maps applied, and if these interfaces are reachable from untrusted networksAffected if The device accepts IKE packets on reachable IPv4 or IPv6 addresses
The device is affected only if it runs exactly Cisco IOS version 15.1, has IKEv1 configured and enabled, and has exposed IKEv1 interfaces reachable over IPv4 or IPv6.
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 Cisco IOS patch for Bug ID CSCth81055 (upgrade to a fixed IOS version). As an interim control, consider restricting IKE traffic at network boundaries to trusted sources if full VPN functionality can be temporarily limited.
Fix this in iOS
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1144 — 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-2013-1144 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