# CVE-2017-3190: Weak cryptography in Flash Seats Mobile App

> Flash Seats mobile apps fail to validate SSL certificates, allowing attackers to perform man-in-the-middle attacks and intercept data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x77c-2rv5-hhqq

## What is CVE-2017-3190?

CVE-2017-3190 is a high-severity vulnerability in Flash Seats Mobile App, published on 15 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Flash Seats Mobile App for Android version 1.7.9 and earlier and for iOS version 1.9.51 and earlier fails to properly validate SSL certificates provided by HTTPS connections, which may enable an attacker to conduct man-in-the-middle (MITM) attacks.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Axs Flash Seats.

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

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

## Is CVE-2017-3190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3190 is a high-severity vulnerability in Flash Seats Mobile App, published on 15 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3190 in the wild and no public exploit code.

Affected product: Flash Seats Mobile App. 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-3190/ (Markdown: https://insights.sbomify.com/CVE-2017-3190/index.md)
```

## Sources

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

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