dbcve.org
iOSOperating system · Cisco

CVE-2015-4202

MEDIUM · 5.0 CVSS v2.0 Published 2015-06-20
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 IOS 12.2SCH on uBR10000 router Cable Modem Termination Systems (CMTS) does not properly restrict access to the IP Detail Record (IPDR) service, which allows remote attackers to obtain potentially sensitive MAC address and network-utilization information via crafted IPDR packets, aka Bug ID CSCua39203.

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

Cisco IOS 12.2SCH on uBR10000 router CMTS platforms does not enforce proper access controls on the IP Detail Record (IPDR) service. Remote attackers can send crafted IPDR packets to the service to retrieve potentially sensitive MAC addresses and network utilization statistics without authentication.

MitigationRestrict access to the IPDR service by implementing ACLs or network segmentation to limit which hosts can communicate with the IPDR port. Consider upgrading to a patched IOS version if available.

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:= 12.2\(33\)sch= 12.2sch

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

AV:N/AC:L/Au:N/C:P/I:N/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
    Run 'show version' or 'show hardware' to confirm the device is a Cisco uBR10000 series CMTS router
    Affected if Device is NOT a uBR10000 CMTS platform (vulnerability only affects this specific hardware)
  2. Check the IOS version
    Run 'show version' and locate the IOS version string. The affected versions are exactly 12.2(33)sch or 12.2sch
    Affected if IOS version is exactly 12.2(33)sch or 12.2sch (these are the only affected versions per the CVE)
  3. Verify IPDR service is enabled
    Run 'show ipdr' or 'show running-config | include ipdr' to check if the IPDR feature is configured on the device
    Affected if IPDR service is enabled and configured (the vulnerability only applies when IPDR is running)
  4. Check IPDR port accessibility
    Run 'show ipdr session' or check the configured IPDR port (default is 3337) with 'show control-plane host service' to determine if the service is reachable from network interfaces
    Affected if IPDR service is listening and reachable from untrusted networks (remote attackers need network access to exploit)

You are affected only if you are running exactly IOS 12.2(33)sch or 12.2sch on a uBR10000 CMTS router with the IPDR service enabled and accessible from untrusted networks.

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

Restrict access to the IPDR service by implementing ACLs or network segmentation to limit which hosts can communicate with the IPDR port. Consider upgrading to a patched IOS version if available.

Fix this in iOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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