CVE-2017-13107
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 · uneditedLive.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.
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 Live.me Android application (v3.7.20) embeds a hard-coded encryption key directly in its codebase. Anyone who obtains the APK (through app stores or other means) can decompile it, extract this key, and decrypt any data that was encrypted using it. This is a fundamental cryptographic key management failure.
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= 3.7.20CVSS 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.1/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 installed Live.me versionOn the Android device, go to Settings > Apps > Live.me and check the version, or use 'adb shell dumpsys package com.meeloo' via ADB to retrieve version infoAffected if Version equals 3.7.20 exactly
-
Obtain the APK fileExtract the APK from the device using 'adb shell pm path com.meeloo' to get the path, then pull it with 'adb pull'Affected if APK file is successfully obtained for analysis
-
Decompile the APKUse apktool or jadx to decompile the APK. Run 'apktool d live.me.apk' or open the APK in jadx-gui to access the source codeAffected if Decompiled code is available for inspection
-
Search for hardcoded encryption key in stringsSearch the decompiled resources (res/values/strings.xml) and smali files for suspicious string constants that look like encryption keys - typically long alphanumeric strings or Base64-encoded content used in cryptographic contextsAffected if A hardcoded key string or byte array is found embedded in the code
-
Trace key usage in encryption operationsExamine the decompiled Java/smali code to see if the found key is passed to Cipher, SecretKeySpec, or other encryption APIs. Search for method calls involving AES, encrypt, decrypt with the key constantAffected if The hardcoded key is actually used in encryption or decryption operations
If the installed version is 3.7.20 and a hardcoded encryption key is found and used in the application's code, the environment is affected by this vulnerability.
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 dataReplace the hard-coded key with proper key management: either use Android Keystore for key protection, or implement key derivation from user credentials. Identify all encryption operations using the hardcoded key and refactor them to use the new key management approach.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13107 — 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-13107 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