dbcve.org
Videoscape Distribution Suite For Internet StreamingApplication · Cisco

CVE-2016-1353

MEDIUM · 5.3 CVSS v3.0 Published 2016-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 TCP implementation in Cisco Videoscape Distribution Suite for Internet Streaming (VDS-IS) 3.3(0), 3.3(1), 4.0(0), and 4.1(0) does not properly initiate new TCP sessions when a previous session is in a FIN wait state, which allows remote attackers to cause a denial of service (TCP outage) via vectors involving FIN packets, aka Bug ID CSCuy45136.

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

In Cisco VDS-IS, the TCP stack fails to properly initiate new TCP sessions when prior sessions remain in FIN_WAIT state. Attackers can send crafted FIN packets to trigger this condition, causing the system to reject all new TCP connections and resulting in a denial of service.

MitigationApply the vendor patch from Cisco for VDS-IS versions 3.3(x), 4.0(x), and 4.1(x). If no patch is available, consider network-level controls to limit FIN packet abuse and plan for upgrade to a fixed version.

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 Distribution Suite For Internet StreamingApplication
Affected:= 3.3.0= 3.3.1= 4.0.0= 4.1.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Confirm Cisco VDS-IS is installed
    Locate the VDS-IS installation directory or check system services for VDS-IS processes. On the CLI, run 'show version' or look for 'VDS-IS' in the system documentation.
    Affected if The system does not have Cisco VDS-IS installed - this CVE does not apply.
  2. Identify the installed VDS-IS version
    Run the VDS-IS version command, typically 'vds-is version' or check the installation logs and release notes in the installation directory. Compare the version number to the affected list: 3.3.0, 3.3.1, 4.0.0, or 4.1.0.
    Affected if The installed version is exactly 3.3.0, 3.3.1, 4.0.0, or 4.1.0 - these versions are affected by the vulnerability.
  3. Check for TCP connections stuck in FIN_WAIT_2 state
    Run 'netstat -an | grep FIN_WAIT_2' or 'show tcp connections' on the VDS-IS CLI to view all TCP connections currently in FIN_WAIT_2 state. An abnormally high number of these connections indicates the condition may be triggered.
    Affected if A large number of connections remain in FIN_WAIT_2 state and new TCP connections fail to establish.
  4. Test ability to establish new TCP connections
    Attempt to open a new TCP connection to the VDS-IS service from a client or run a connection test. If connections are refused or timeout while the system appears otherwise operational, the vulnerability may be active.
    Affected if New TCP connections are rejected or time out while prior connections are stuck in FIN_WAIT_2 state.

A system is affected if it runs Cisco VDS-IS version 3.3.0, 3.3.1, 4.0.0, or 4.1.0 and exhibits stuck FIN_WAIT_2 connections that prevent new TCP sessions from establishing.

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 vendor patch from Cisco for VDS-IS versions 3.3(x), 4.0(x), and 4.1(x). If no patch is available, consider network-level controls to limit FIN packet abuse and plan for upgrade to a fixed version.

Fix this in Videoscape Distribution Suite For Internet Streaming Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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