# CVE-2017-14486: Weak cryptography in n/a

> Attackers can sniff network traffic to steal user credentials and messages from Vibease apps due to cleartext transmission and weak authentication.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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:** 1 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x7m9-39j4-mh2q

## What is CVE-2017-14486?

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

### Official description

The 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 2 products.


Products: Vibease Chat, Vibease Wireless Remote Vibrator.

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

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

## Is CVE-2017-14486 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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