iOSOperating system · Cisco

CVE-2015-4199

HIGH · 7.1 CVSS v2.0 Published 2015-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Race condition in the IPv6-to-IPv4 functionality in Cisco IOS 15.3S in the Performance Routing Engine (PRE) module on UBR devices allows remote attackers to cause a denial of service (NULL pointer free and module crash) by triggering intermittent connectivity with many IPv6 CPE devices, aka Bug ID CSCug47366.

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 confidence

Race condition in the IPv6-to-IPv4 functionality in Cisco IOS 15.3S in the Performance Routing Engine (PRE) module on UBR devices allows remote attackers to cause a NULL pointer dereference leading to module crash and denial of service by triggering intermittent connectivity with many IPv6 CPE devices.

MitigationApply the Cisco IOS 15.3S security update addressing CSCug47366. As an interim measure, limit exposure of affected UBR devices and monitor for signs of the described attack pattern involving intermittent IPv6 CPE connectivity.

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
Affected:= 15.3s

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/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 checks

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

  1. Identify the Cisco IOS version
    Execute 'show version' on the device CLI and locate the version string in the output
    Affected if The version shown is exactly 15.3S (or a specific 15.3Sx release that falls within the 15.3S train)
  2. Confirm the device is a UBR platform
    Execute 'show version' or 'show platform' and check the hardware platform type; UBR devices are cable broadband routers
    Affected if The device model is a UBR-series router (e.g., UBR10012, UBR7200)
  3. Verify IPv6-to-IPv4 feature is configured
    Check the running configuration with 'show running-config' for IPv6 transition features such as NAT64, 464XLAT, or IPv6 tunnel interfaces
    Affected if IPv6-to-IPv4 translation or tunneling features are enabled in the configuration
  4. Check for Performance Routing Engine (PRE) module usage
    Execute 'show module' or 'show platform' to verify the PRE module is present and active on the UBR device
    Affected if The PRE module is installed and running on the device

A user is affected if they are running Cisco IOS 15.3S on a UBR device with an active PRE module and IPv6-to-IPv4 translation features enabled, as the race condition triggers when intermittent IPv6 CPE connectivity occurs.

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

Apply the Cisco IOS 15.3S security update addressing CSCug47366. As an interim measure, limit exposure of affected UBR devices and monitor for signs of the described attack pattern involving intermittent IPv6 CPE connectivity.

Fix this in iOS Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4199 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4199 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