dbcve.org
Videoscape Delivery System For Internet StreamerApplication · Cisco

CVE-2015-0671

MEDIUM · 5.0 CVSS v2.0 Published 2015-03-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
The DNS implementation in Cisco Videoscape Distribution Suite for Internet Streaming (VDS-IS) 3.2(1) allows remote attackers to cause a denial of service (CPU consumption and network-resource consumption) via crafted packets, aka Bug ID CSCun15911.

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

The DNS implementation in Cisco Videoscape Distribution Suite for Internet Streaming (VDS-IS) version 3.2(1) contains a vulnerability that allows remote attackers to cause denial of service through crafted DNS packets. The attack triggers excessive CPU and network resource consumption, potentially rendering the system unavailable.

MitigationApply the Cisco patch for bug ID CSCun15911 to the affected VDS-IS 3.2(1) installation. As an interim control, implement network-level filtering to block suspicious DNS packets targeting the affected system.

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
Videoscape Delivery System For Internet StreamerApplication
Affected:= 3.2.1

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

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

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 Cisco VDS-IS installation and version
    Locate the Cisco Videoscape Distribution Suite for Internet Streaming installation directory and check the version file or use system commands to query the installed software version (e.g., 'show version' or check /opt/vds directory for version files).
    Affected if The installed version is exactly 3.2.1 or 3.2(1)
  2. Confirm DNS service is enabled
    Check the VDS-IS configuration to determine if the DNS service/module is enabled. Look for DNS-related configuration files in the VDS-IS config directory or use the VDS-IS admin interface to view running services.
    Affected if DNS service is enabled and listening for DNS queries on the system
  3. Verify DNS service is network-exposed
    Check network listener configurations and firewall rules to determine if the DNS service port (typically UDP/TCP port 53) is exposed to network traffic. Use 'netstat -anp' or 'ss -ln' to list listening services.
    Affected if DNS port 53 is bound to a network interface accessible from outside the local host
  4. Monitor for abnormal DNS-related resource consumption
    Use system monitoring tools (top, sar, or similar) to observe CPU usage and network traffic specifically related to DNS processes. Check for unusually high CPU usage by dns-related processes or excessive DNS network traffic.
    Affected if DNS processes are consuming excessive CPU or network bandwidth beyond normal operational levels
  5. Review DNS packet processing logs
    Examine VDS-IS logs for DNS service, looking for patterns of malformed packets, high request volumes, or error messages indicating packet processing issues.
    Affected if Logs show large volumes of DNS requests or evidence of malformed packet handling

A user is affected if they have Cisco VDS-IS version 3.2(1) installed with the DNS service enabled and exposed to network traffic.

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 patch for bug ID CSCun15911 to the affected VDS-IS 3.2(1) installation. As an interim control, implement network-level filtering to block suspicious DNS packets targeting the affected system.

Fix this in Videoscape Delivery System For Internet Streamer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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