CVE-2021-25418
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 component protection vulnerability in Samsung Internet prior to version 14.0.1.62 allows untrusted applications to execute arbitrary activity in specific condition.
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 confidenceImproper component protection vulnerability in Samsung Internet browser allows untrusted applications to invoke browser components and execute arbitrary activities under specific conditions. The vulnerability stems from inadequate access controls on Android components exported by the browser application, enabling potential unauthorized interactions from other apps on the same device.
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< 14.0.1.62CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Verify Samsung Internet browser is installedOn the Android device, go to Settings > Apps > Apps, then search for 'Samsung Internet' or 'Samsung Internet Browser' in the application list. Alternatively, check if the app icon appears in the app drawer.Affected if Samsung Internet browser appears in the installed applications list
-
Determine the installed version numberIn Settings > Apps > Apps > Samsung Internet, tap on 'App info' or 'About app' to view the version number. Note the version displayed (for example, it may show as '14.0.1.51' or similar).Affected if A version number is displayed in the app information screen
-
Compare version to the affected rangeCompare the installed version number to 14.0.1.62. If the installed version is lower (for example, 14.0.1.50, 13.x.x.x, etc.), the version falls within the vulnerable range.Affected if The installed version is a three-part number less than 14.0.1.62 (for example, 14.0.1.50, 13.0.2.15, etc.)
-
Confirm the vulnerability applies to your device modelThis vulnerability affects Samsung Internet on Samsung Android devices. Verify the device is a Samsung Android device running Samsung Internet as the browser application.Affected if The device is a Samsung Android device with Samsung Internet as the default or installed browser
A user is affected if Samsung Internet browser version 14.0.1.62 or higher is not installed on their Samsung Android device.
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 data14.0.1.62
Update Samsung Internet browser to version 14.0.1.62 or later to obtain the vendor patch that implements proper component protection. For enterprise environments, ensure mobile device management policies enforce the browser update.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25418 — 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-25418 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