# CVE-2017-5887: Security feature bypass in n/a

> An SSL Pinning bypass in Starscream allows attackers to intercept secure WebSocket connections by exploiting late certificate validation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 6 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h3px-rcqp-mvf3

## What is CVE-2017-5887?

CVE-2017-5887 is a high-severity vulnerability in n/a, published on 6 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebSocket.swift in Starscream before 2.0.4 allows an SSL Pinning bypass because pinning occurs in the stream function (this is too late; pinning should occur in the initStreamsWithData function).

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Starscream Project Starscream.

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

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

## Is CVE-2017-5887 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7192](https://insights.sbomify.com/CVE-2017-7192/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5887 is a high-severity vulnerability in n/a, published on 6 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-2017-5887 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-2017-5887/ (Markdown: https://insights.sbomify.com/CVE-2017-5887/index.md)
```

## Sources

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

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