dbcve.org
Ios XrOperating system · Cisco

CVE-2015-0694

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Cisco ASR 9000 devices with software 5.3.0.BASE do not recognize that certain ACL entries have a single-host constraint, which allows remote attackers to bypass intended network-resource access restrictions by using an address that was not supposed to have been allowed, aka Bug ID CSCur28806.

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 confidence

Cisco ASR 9000 devices running software version 5.3.0.BASE fail to properly interpret single-host constraint ACL entries, allowing remote attackers to bypass network access restrictions by using IP addresses that should have been blocked.

MitigationUpgrade to a patched version of Cisco IOS XR software beyond 5.3.0.BASE and verify ACL configurations properly enforce single-host constraints.

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
Affected:= 5.3.0_base
Asr 9001Hardware / appliance
Affected:all versions
Asr 9006Hardware / appliance
Affected:all versions
Asr 9010Hardware / appliance
Affected:all versions
Asr 9904Hardware / appliance
Affected:all versions
Asr 9912Hardware / appliance
Affected:all versions
Asr 9922Hardware / appliance
Affected:all versions

CVSS 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
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Execute 'show version' or 'show platform' on the device CLI and look for ASR 9000 series model identifiers (ASR 9001, ASR 9006, ASR 9010, ASR 9904, ASR 9912, ASR 9922)
    Affected if The device is any of the listed ASR models (9001, 9006, 9010, 9904, 9912, 9922)
  2. Check the IOS XR software version
    Execute 'show version' and locate the software version string. Look for version '5.3.0.BASE' specifically, or any version in the 5.3.0.x branch
    Affected if The device runs IOS XR version 5.3.0.BASE or falls within the affected version range
  3. Identify configured ACLs with single-host constraints
    Execute 'show access-lists' or 'show ip access-lists' to list all configured ACLs. Search for entries using the 'host' keyword format (e.g., 'permit host 10.1.1.1' or 'deny host 192.168.1.100')
    Affected if Any ACL contains single-host entries using the 'host' keyword syntax
  4. Verify the ACL is applied to an interface
    Execute 'show access-lists interface' or 'show running-config | include access-group' to determine if the vulnerable ACL is actively applied to an interface
    Affected if An ACL with single-host entries is applied to a physical or logical interface inbound or outbound

The device is affected if it is an ASR 9000 series running IOS XR 5.3.0.BASE and has an ACL with single-host constraint entries applied to an interface, because the single-host ACL entries may not be correctly enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Cisco IOS XR software beyond 5.3.0.BASE and verify ACL configurations properly enforce single-host constraints.

Fix this in Ios Xr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0694 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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