Ios XrOperating system · Cisco
CVE-2015-0695
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 XR 4.3.4 through 5.3.0 on ASR 9000 devices, when uRPF, PBR, QoS, or an ACL is configured, does not properly handle bridge-group virtual interface (BVI) traffic, which allows remote attackers to cause a denial of service (chip and card hangs and reloads) by triggering use of a BVI interface for IPv4 packets, aka Bug ID CSCur62957.
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 confidenceCisco IOS XR versions 4.3.4 through 5.3.0 on ASR 9000 routers have a denial of service vulnerability in the handling of bridge-group virtual interface (BVI) traffic when uRPF, PBR, QoS, or ACL features are configured. Attackers can trigger the vulnerability by sending IPv4 packets through a BVI interface, causing the network processor chip to hang and forcing card reloads.
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 XrOperating system
= 4.3.0= 4.3.1= 4.3.2= 4.3.3= 5.1.0= 5.1.1= 5.1.2= 5.2.0= 5.2.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.
-
Identify the hardware modelRun 'show inventory' or check the physical device label to confirm the router is an ASR 9000 seriesAffected if The device is an ASR 9000 router - other Cisco devices are not affected by this CVE
-
Check the IOS XR versionRun 'show version' and locate the IOS XR version number in the outputAffected if The version falls within 4.3.0 through 5.3.0, specifically 4.3.0, 4.3.1, 4.3.2, 4.3.3, 5.1.0, 5.1.1, 5.1.2, 5.2.0, or 5.2.1
-
Verify BVI interface configurationRun 'show run interface BVI' or 'show ip interface brief' to list all BVI interfaces configured on the systemAffected if Any bridge-group virtual interface (BVI) is configured and active on the device
-
Check for triggering features on BVIRun 'show run' and search for 'urpf', 'pbr', 'qos', or 'acl' applied to BVI interfaces, or examine BVI interface configurations with 'show run interface BVI <number>'Affected if Any of uRPF, PBR, QoS, or ACL features are configured in conjunction with BVI interfaces
The system is affected if it is an ASR 9000 router running IOS XR versions 4.3.0-5.2.1 with BVI interfaces that have uRPF, PBR, QoS, or ACL features enabled.
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 XR to a patched version beyond 5.3.0. Until upgrade is possible, review configurations to identify and potentially disable or modify the combination of BVI interfaces with uRPF, PBR, QoS, or ACL features that trigger the issue.
Fix this in Ios Xr
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-2015-0695 — 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-0695 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