CVE-2017-14486
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 · uneditedThe Vibease Wireless Remote Vibrator app for Android and the Vibease Chat app for iOS use cleartext to exchange messages with other apps and the PLAIN SASL mechanism to send auth tokens to Vibease servers, which allows remote attackers to obtain user credentials, messages, and other sensitive information by sniffing the network for XMPP traffic.
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 Vibease Wireless Remote Vibrator app for Android and Vibease Chat app for iOS transmit XMPP messages and authentication tokens in cleartext without encryption, and use the PLAIN SASL mechanism which sends credentials in base64-encoded plain text. An attacker on the network can sniff this traffic and capture user credentials, messages, and other sensitive data.
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 dataall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify if Vibease apps are installedCheck Android device for 'Vibease Wireless Remote Vibrator' app or iOS device for 'Vibease Chat' app. On Android, use 'pm list packages' or check app settings. On iOS, check installed apps list.Affected if Either Vibease app is present on the device, making the user potentially affected by cleartext transmission vulnerability.
-
Capture and inspect outgoing network trafficUse a network packet capture tool (such as Wireshark, tcpdump, or a mobile proxy) to intercept traffic from the device running the Vibease app. Filter for XMPP traffic on port 5222 or raw TCP connections.Affected if XMPP traffic is transmitted without TLS encryption (no SSL/TLS wrapper), appearing as readable plain text in the capture.
-
Verify PLAIN SASL authentication is in useAnalyze the captured XMPP traffic for the authentication mechanism. Look for the '<auth mechanism="PLAIN"' element in the XML stream or base64-encoded credential strings sent during the authentication handshake.Affected if The PLAIN SASL mechanism is used, sending credentials as base64-encoded plain text rather than using a secure mechanism like SCRAM-SHA-1.
-
Confirm sensitive data is exposed in cleartextInspect captured packets for user credentials, authentication tokens, and message content. These should appear as readable ASCII or base64-encoded text rather than encrypted ciphertext.Affected if User credentials, XMPP messages, or authentication tokens are visible in plain text or base64 form within the network capture.
A user is affected if they have either Vibease app installed AND network traffic analysis reveals unencrypted XMPP communications using PLAIN SASL authentication.
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 dataImplement TLS encryption for all XMPP communications and replace PLAIN SASL authentication with a secure mechanism like SCRAM-SHA-1 or certificate-based authentication.
- 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-14486 — 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-14486 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