CVE-2020-12483
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 appstore before 8.12.0.0 exposes some of its components, and the attacker can cause remote download and install apps through carefully constructed parameters.
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 · moderate confidenceThe appstore application before version 8.12.0.0 has exposed Android components (likely activities or services) that can be invoked with malicious parameters, allowing an attacker to trigger remote download and installation of arbitrary applications. This is a classic insecure component exposure vulnerability where input validation and permission checks are missing on exported components.
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< 8.12.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check if Vivo Appstore is installedRun 'adb shell pm list packages | grep -i vivo.appstore' or 'adb shell pm list packages com.vivo.appstore' to see if the package exists on the deviceAffected if The package is not found, the user is not affected by this specific vulnerability in Vivo Appstore
-
Get the installed version of Vivo AppstoreRun 'adb shell dumpsys package com.vivo.appstore' and look for 'versionName' or 'versionCode' in the output. Alternatively, use 'adb shell pm dump com.vivo.appstore | grep version'Affected if The version displayed is blank or the package does not exist, indicating the app is not installed
-
Compare installed version against the affected rangeIf versionName is shown, compare it to 8.12.0.0. Note that version names may appear as numeric strings like '8.11.5.0' - these are lexicographically comparableAffected if The installed version is less than 8.12.0.0 (for example, 8.11.0.0, 8.10.5.0, etc.), the device is vulnerable to the exposed component attack
-
Verify exported components exist (optional confirmation)Run 'adb shell dumpsys package com.vivo.appstore' and look for 'android:exported=true' under <activity> or <service> tags in the package dumpAffected if Exported activities or services are present in the package dump, confirming the insecure component exposure that enables the attack vector
If Vivo Appstore is installed and its version is less than 8.12.0.0, the device 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 data8.12.0.0
Update the appstore to version 8.12.0.0 or later, which presumably adds proper permission checks and input validation on the exposed components to prevent unauthorized app installation.
- 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-12483 — 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-12483 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