CVE-2017-3190
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlash 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Flash Seats mobile app for Android (1.7.9 and earlier) and iOS (1.9.51 and earlier) does not properly validate SSL certificates when establishing HTTPS connections. This allows attackers on the same network to intercept encrypted traffic by performing man-in-the-middle attacks, potentially exposing sensitive user data transmitted through the app.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.9.51<= 1.7.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android app versionOpen the Google Play Store app, search for 'Flash Seats' or 'Axs Flash Seats', tap on the app, and view the version number under 'Additional information'. Alternatively, check the app version in device Settings > Apps > Flash Seats > App info.Affected if The installed version is 1.7.9 or earlier
-
Check iOS app versionOpen the App Store app, search for 'Flash Seats' or 'Axs Flash Seats', tap on the app, and view the version number in the app description. Alternatively, check via iPhone Settings > General > iPhone Storage > Flash Seats.Affected if The installed version is 1.9.51 or earlier
-
Determine network exposureConsider whether the device with the vulnerable app version has been used on untrusted or public WiFi networks where an attacker could perform a man-in-the-middle attack.Affected if The vulnerable app version was used on shared or untrusted networks, as this is the attack vector for exploiting improper SSL validation
You are affected if the installed Flash Seats app version is 1.7.9 or earlier on Android, or 1.9.51 or earlier on iOS, and the app was used on networks where interception was possible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the mobile app to a version that implements proper SSL certificate validation, including certificate chain validation, hostname verification, and consideration of certificate pinning for sensitive endpoints. Until updated, users should avoid using the app on untrusted networks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3190 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data