# CVE-2017-15533: Weak cryptography in SSL Visibility (SSLV)

> Remote attackers can decrypt captured SSL sessions by exploiting a padding oracle vulnerability in Symantec SSL Visibility appliances.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g56c-h972-7rhp

## What is CVE-2017-15533?

CVE-2017-15533 is a medium-severity vulnerability in Symantec Corporation SSL Visibility (SSLV), published on 17 May 2018. 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.10 prior to 3.10.4.1, 3.11, and 3.12 prior to 3.12.2.1 are vulnerable to the Return of the Bleichenbacher Oracle Threat (ROBOT) attack. All affected SSLV versions act as weak oracles according the oracle classification used in the ROBOT research paper. A remote attacker, who has captured a pre-recorded SSL session inspected by SSLV, can establish multiple millions of crafted SSL connections to the target and obtain the session keys required to decrypt the pre-recorded SSL session.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2017-15533?

It affects 1 product.


Products: Broadcom Ssl Visibility Appliance.

## How do I fix CVE-2017-15533?

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

## Is CVE-2017-15533 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15533 and fix it if it is affected.

What it is: CVE-2017-15533 is a medium-severity vulnerability in Symantec Corporation SSL Visibility (SSLV), published on 17 May 2018. 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-2017-15533 in the wild and no public exploit code.

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

## Sources

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

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