CVE-2021-25354
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 input check in Samsung Internet prior to version 13.2.1.46 allows attackers to launch non-exported activity in Samsung Browser via malicious deeplink.
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 Android component hijacking vulnerability in Samsung Internet browser where improper input validation on deeplinks allows external attackers to launch non-exported (internal) activities. Attackers can craft malicious deeplinks that bypass the intended access controls and trigger internal app components that should not be accessible from outside the application context.
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< 13.2.1.46CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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 Samsung Internet browser is installedCheck the app list on the Samsung Android device. Navigate to Settings > Apps, or use ADB command: adb shell pm list packages | grep samsung.internetAffected if Samsung Internet browser package (com.sec.android.app.sbrowser) is present on the device
-
Retrieve the installed version numberIn Settings > Apps > Samsung Internet > App info, note the version number displayed. Alternatively, use ADB: adb shell dumpsys package com.sec.android.app.sbrowser | grep versionNameAffected if A version number is returned from the package manager query
-
Compare installed version against vulnerable rangeParse the version number from step 2. The affected range is any version earlier than 13.2.1.46. Compare numerically: if the version is 13.2.1.45 or lower, or any 13.0.x or 12.x.x release, the device is vulnerableAffected if The installed version is less than 13.2.1.46 (for example, 13.2.1.45, 13.0.0.80, 12.1.0.50, etc.)
-
Confirm deeplink handling is enabledVerify the browser has not been configured to disable deeplinks. Check Settings > Samsung Internet > Privacy and security > Browsing mode. Default installations have deeplinks enabledAffected if Samsung Internet is in use with default or custom browsing modes that allow deeplink processing (most default configurations)
A Samsung Android device is affected if Samsung Internet browser is installed and its version is below 13.2.1.46, with deeplink handling enabled in the browser settings.
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 data13.2.1.46
Users should update Samsung Internet browser to version 13.2.1.46 or later, which contains the proper input validation fix. Organizations managing Samsung devices should ensure this update is deployed via mobile device management (MDM) systems.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25354 — 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-25354 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