CVE-2017-13107: Live.me - live stream video chat, 3.7.20, 2017-11-06, Android application uses a hard-coded key for encryption
CVE-2017-13107 is a high-severity flaw (CVSS 7.5) affecting liveme. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Live.me - live stream video chat, 3.7.20, 2017-11-06, Android application uses a hard-coded key for encryption. Data stored using this key can be decrypted by anyone able to access this key.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.0% (top 39%) |
| CISA exploited list | No |
| Weakness | CWE-798 |
| Published | 2018-08-15 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-13107?
liveme: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-13107 being exploited?
CVE-2017-13107 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-13107 affect?
CVE-2017-13107 affects liveme. Severity is high (CVSS 7.5). Live.me - live stream video chat, 3.7.20, 2017-11-06, Android application uses a hard-coded key for encryption. Data stored using this key can be decrypted by anyone able to access this key.
How urgent is CVE-2017-13107?
Priority 47/100. High severity; Remotely exploitable, no login, no user action