CVE-2020-10834
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 on Samsung mobile devices with P(9.0) software. Attackers can view notifications on the lock screen via Routines. The Samsung ID is SVE-2019-15074 (February 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 · high confidenceThis vulnerability in Samsung mobile devices running Android P (9.0) allows attackers to view notifications on the lock screen through the Routines feature. The issue is an information disclosure flaw where the Routines functionality bypasses lock screen notification privacy protections.
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= 9.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Android version is 9.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version shows exactly 9.0 (Android Pie) - versions before or after this release are not affected by this specific CVE
-
Confirm device is a Samsung mobile deviceCheck Settings > About Phone > Model number, or run 'getprop ro.product.model' via ADBAffected if Device is a Samsung phone or tablet - this vulnerability affects Samsung mobile devices specifically, not other Android manufacturers
-
Verify if Routines feature is enabledOpen Samsung Galaxy Store or Settings > Bixby > Routines (or Settings > Modes and Routines depending on One UI version), check if any routines are activeAffected if Routines feature is turned on and active - the vulnerability exploits this feature to bypass lock screen privacy
-
Check Samsung security patch levelGo to Settings > About Phone > Software information > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than February 2020 (SVE-2019-15074) - the patch that fixes this issue was released in February 2020
Device is affected if it is a Samsung mobile device running Android 9.0, has Routines enabled, and has a security patch level before February 2020.
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 February 2020 security patch (SVE-2019-15074) or later. As a workaround, consider disabling the Routines feature or using additional lock screen security measures until the patch is applied.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10834 — 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-10834 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