CVE-2020-6869
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 · uneditedAll versions up to 10.06 of ZTEMarket APK are impacted by an information leak vulnerability. Due to Activity Component exposure users can exploit this vulnerability to get the private cookie and execute silent installation.
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 confidenceZTEMarket APK versions up to 10.06 contain an exported Activity component that leaks sensitive information. The exposed Activity allows external malicious apps to retrieve private cookies stored by the application and perform silent (background) APK installations without user consent, due to improper access control on the component.
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<= 10.06CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 ZTE Ztemarket app is installedCheck the device or app inventory for the presence of the ZTE Ztemarket application. On Android, you can list installed packages using 'pm list packages' or check via device management tools.Affected if The app is present on the device or in your managed app inventory.
-
Determine the installed version of ZTE ZtemarketRetrieve the version of the installed ZTE Ztemarket APK. On Android, use 'dumpsys package com.zte.ztmarket' or check the app version through package manager. Compare the version name or version code against 10.06.Affected if The installed version is 10.06 or lower.
-
Inspect AndroidManifest.xml for exported Activity componentsDecompile the APK using tools like apktool or jadx and examine the AndroidManifest.xml file. Look for <activity> elements with android:exported="true" attribute.Affected if Any sensitive Activity component is found with android:exported="true" without proper android:permission protection.
-
Verify access control on the vulnerable ActivityIn the decompiled AndroidManifest.xml, check if the Activity that handles cookies or APK installation has android:permission defined. Also review the Activity's source code (smali or Java) to confirm it performs sensitive operations like retrieving cookies or installing APKs.Affected if The Activity handling cookies or APK installation is exported without android:permission attribute or other access control measures.
A device is affected if ZTE Ztemarket APK version 10.06 or lower is installed and contains an exported Activity component without proper access controls that handles sensitive cookie data or APK installation functionality.
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 dataSet android:exported="false" for sensitive Activity components in AndroidManifest.xml, or implement proper permission checks (android:permission) for those that must be exported. Review and secure any functionality that handles cookies or app installation to prevent unauthorized access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6869 — 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-2020-6869 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