# CVE-2016-10259: Denial of service in SSL Visibility

> A malicious SSL client can exhaust the TCP connection pool of Symantec SSL Visibility servers, causing a denial of service for intercepted connections.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2vpg-j5v7-47x2

## What is CVE-2016-10259?

CVE-2016-10259 is a medium-severity denial of service vulnerability in Symantec Corporation SSL Visibility, published on 11 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symantec SSL Visibility (SSLV) 3.8.4FC, 3.9, 3.10 before 3.10.4.1, and 3.11 before 3.11.3.1 is susceptible to a denial-of-service vulnerability that impacts the SSL servers for intercepted SSL connections. A malicious SSL client can, under certain circumstances, temporarily exhaust the TCP connection pool of an SSL server.

Weakness: CWE-399

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

It affects 4 products.


Products: Bluecoat Ssl Visibility Appliance Sv1800 Firmware, Bluecoat Ssl Visibility Appliance Sv2800 Firmware, Bluecoat Ssl Visibility Appliance Sv3800 Firmware, Bluecoat Ssl Visibility Appliance Sv800 Firmware.

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

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

## Is CVE-2016-10259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10259 is a medium-severity denial of service vulnerability in Symantec Corporation SSL Visibility, published on 11 Apr 2017. 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-10259 in the wild and no public exploit code.

Affected product: Symantec Corporation SSL Visibility. 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-10259/ (Markdown: https://insights.sbomify.com/CVE-2016-10259/index.md)
```

## Sources

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

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