iOSOperating system · Cisco
CVE-2013-1148
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 · uneditedThe General Responder implementation in the IP Service Level Agreement (SLA) feature in Cisco IOS 15.2 and IOS XE 3.1.xS through 3.4.xS before 3.4.5S and 3.5.xS through 3.7.xS before 3.7.2S allows remote attackers to cause a denial of service (device reload) via crafted (1) IPv4 or (2) IPv6 IP SLA packets on UDP port 1167, aka Bug ID CSCuc72594.
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 General Responder component of Cisco's IP Service Level Agreement (SLA) feature allows unauthenticated remote attackers to cause a denial of service by sending specially crafted IPv4 or IPv6 IP SLA packets to UDP port 1167, triggering a device reload. The vulnerability affects IOS 15.2 and IOS XE versions 3.1.xS through 3.4.xS before 3.4.5S, and 3.5.xS through 3.7.xS before 3.7.2S.
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
Ios XeOperating system
= 3.1.0s= 3.1.1s= 3.1.2s= 3.1.3s= 3.1.4s= 3.2.0s= 3.2.1s= 3.2.2s= 3.3.0s= 3.3.1s= 3.3.2s= 3.3.3sCVSS 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.
-
Identify the IOS or IOS XE versionRun 'show version' and note the exact software version number (for IOS, look for 'Version 15.2...' or similar; for IOS XE, look for 'Version 3.1.xS' through '3.7.xS')Affected if The version is 15.2, or any 3.1.xS through 3.4.xS version before 3.4.5S, or any 3.5.xS through 3.7.xS version before 3.7.2S
-
Confirm IP SLA feature is configuredRun 'show ip sla configuration' or 'show run | include sla' to see if IP SLA operations are defined on the deviceAffected if Any IP SLA operations are configured and active
-
Verify General Responder is enabledRun 'show ip sla responder' to check if the IP SLA responder is enabledAffected if The responder status shows it is enabled and listening for IP SLA requests
-
Check if UDP port 1167 is accessibleAttempt to reach UDP port 1167 from an external source, or verify the device is listening on this port (often shown in 'show ip sockets' or 'show udp' output)Affected if UDP port 1167 is open and reachable on the device interfaces
The device is affected if it runs a vulnerable IOS/IOS XE version (15.2, 3.1.xS-3.4.xS before 3.4.5S, or 3.5.xS-3.7.xS before 3.7.2S) AND has IP SLA General Responder enabled with UDP port 1167 accessible.
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/IOS XE to version 3.4.5S or later (for 3.4.xS branches) or 3.7.2S or later (for 3.5-3.7.xS branches). If upgrade is not immediately feasible, consider blocking UDP port 1167 at network perimeter to prevent external attackers from reaching the vulnerability.
Fix this in iOS
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1148 — 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-1148 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