Ubr10012Hardware / appliance · Cisco
CVE-2013-1189
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 Universal Broadband (aka uBR) 10000 series routers, when an IPv4/IPv6 dual-stack modem is used, allow remote attackers to cause a denial of service (routing-engine reload) via unspecified changes to IP address assignments, aka Bug ID CSCue15313.
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 confidenceThis CVE describes a denial-of-service vulnerability in Cisco Universal Broadband (uBR) 10000 series routers. When these routers operate with IPv4/IPv6 dual-stack modems, remote attackers can trigger an unspecified manipulation of IP address assignments that causes the routing engine to reload, resulting in service disruption.
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
Ubr10012Hardware / appliance
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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/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.
-
Identify the router modelLog into the router CLI and run 'show version' or check the physical device label to confirm the model is Cisco Ubr10012Affected if The device is a Cisco Ubr10012 router - all versions of this model are affected
-
Determine if dual-stack mode is enabledCheck the router configuration for IPv4/IPv6 dual-stack modem support. Use 'show running-config' or review the cable modem configuration to see if both IPv4 and IPv6 addressing are active on the cable interfacesAffected if IPv4/IPv6 dual-stack mode is enabled on the router - this is required for the vulnerability to be exploitable
-
Verify management interface exposureReview the router's access control lists and management interface bindings using 'show ip access-lists' and 'show interface' commands to determine if the management interfaces are reachable from untrusted networksAffected if The management interface is accessible from untrusted/public networks - this enables remote attackers to trigger the vulnerability
A Cisco Ubr10012 router running with IPv4/IPv6 dual-stack modems and exposed management interfaces is vulnerable to CVE-2013-1189, which allows remote attackers to cause routing engine reloads via manipulated IP address assignments.
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 dataRestrict management access to trusted networks and monitor for unusual IP address assignment activity; if available, apply Cisco firmware updates addressing Bug ID CSCue15313.
Fix this in Ubr10012
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1189 — 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-1189 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