# CVE-2016-1353: Denial of service in n/a

> Remote attackers can cause a TCP outage in Cisco Videoscape Distribution Suite by sending FIN packets during specific session states.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fjv2-mj28-xvpf

## What is CVE-2016-1353?

CVE-2016-1353 is a medium-severity denial of service vulnerability in n/a, published on 1 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-399

## Which versions are affected by CVE-2016-1353?

It affects 1 product.


Products: Cisco Videoscape Distribution Suite for Internet Streaming.

## How do I fix CVE-2016-1353?

No fix has been published for CVE-2016-1353 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-1353 being exploited?

There is no known exploitation of CVE-2016-1353 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-0725](https://insights.sbomify.com/CVE-2015-0725/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1353 and fix it if it is affected.

What it is: CVE-2016-1353 is a medium-severity denial of service vulnerability in n/a, published on 1 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1353 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1353/ (Markdown: https://insights.sbomify.com/CVE-2016-1353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1353
- OSV: https://osv.dev/vulnerability/CVE-2016-1353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1353/
Summaries are generated and may contain mistakes; the official description above is the record.