CVE-2021-25505
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 · uneditedImproper authentication in Samsung Pass prior to 3.0.02.4 allows to use app without authentication when lockscreen is unlocked.
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 is an authentication bypass vulnerability in Samsung Pass (versions prior to 3.0.02.4). When a device's lockscreen is already unlocked, the Samsung Pass application can be accessed without requiring its own separate authentication (biometric/PIN), allowing unauthorized access to stored credentials.
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.0.02.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Confirm Samsung Pass is installedNavigate to Settings > Apps on the device and search for Samsung Pass, or use ADB command: adb shell pm list packages | grep -i passAffected if Samsung Pass is not installed - not affected
-
Retrieve the installed Samsung Pass versionIn Settings > Apps > Samsung Pass, tap App info to view the version number, or use ADB: adb shell dumpsys package com.samsung.android.spass | grep versionNameAffected if Unable to determine version - manual verification required
-
Compare version against the affected rangeCheck if the installed version is lower than 3.0.02.4 - any version prior to 3.0.02.4 is affectedAffected if Installed version < 3.0.02.4 - the device is vulnerable to the authentication bypass
-
Verify device lockscreen is configuredGo to Settings > Lock screen > Screen lock type to confirm a PIN, pattern, or password is setAffected if No device lockscreen configured - the bypass has no practical effect but the app code remains vulnerable
If Samsung Pass is installed with version lower than 3.0.02.4 and the device has a lockscreen enabled, the user is affected by this authentication bypass 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.
dbcve · scoped3.0.02.4
Update Samsung Pass to version 3.0.02.4 or later via the Galaxy Store or Google Play Store to receive the vendor patch.
Samsung Pass version 3.0.02.4 or later
- Open the Galaxy Store (Samsung Galaxy Store) app on your Samsung device
- Search for 'Samsung Pass' in the app store
- Tap Update to install Samsung Pass version 3.0.02.4 or later
- Alternatively, go to Settings > Apps > Samsung Pass and check for available updates
- Verify the installed version by checking the app info in Settings > Apps > Samsung Pass
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25505 — 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-2021-25505 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