CVE-2020-35548
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 · uneditedAn issue was discovered in Finder on Samsung mobile devices with Q(10.0) software. A call to a non-existent provider allows attackers to cause a denial of service. The Samsung ID is SVE-2020-18629 (December 2020).
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 confidenceA denial of service vulnerability exists in the Finder application on Samsung mobile devices running Android Q (10.0). The issue occurs when the Finder app attempts to call a non-existent content provider, causing the application to crash or become unresponsive, potentially affecting device usability.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Verify Android version is exactly 10.0Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if Android version shows 10.0 (Android Q)
-
Confirm device is a Samsung modelCheck device model in Settings > About Phone > Model number, or run 'adb shell getprop ro.product.model'Affected if Device is a Samsung model running Android Q
-
Verify Finder app is installedCheck for Finder app in app drawer, or run 'adb shell pm list packages | grep finder'Affected if Finder app is present on the device
-
Check if security update SVE-2020-18629 is appliedGo to Settings > About Phone > Software info > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'Affected if Security patch level is earlier than December 2020 or the SVE-2020-18629 update has not been applied
-
Monitor for Finder app crashesCheck device logs via 'adb logcat' or review crash reports in Settings > Apps > Finder > Crash reports, look for content provider errorsAffected if Finder app exhibits repeated crashes or force-close events
A Samsung device is affected if it runs Android 10.0, has the Finder app installed, and lacks the December 2020 security update SVE-2020-18629.
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 dataApply the Samsung security update (SVE-2020-18629) released in December 2020 to affected devices running Android Q. Until patched, monitor for Finder app crashes and consider restricting access to untrusted content that may trigger the vulnerable code path.
- Consultation8.0 h
- Implementation2.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 $5,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35548 — 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-35548 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