dbcve.org
EmailApplication · Samsung

CVE-2021-25375

MEDIUM · 6.5 CVSS v3.1 Published 2021-04-09
Fix available
A fix is available. Upgrade to 6.1.14.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Using predictable index for attachments in Samsung Email prior to version 6.1.41.0 allows remote attackers to get attachments of another emails when users open the malicious attachment.

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 confidence

Samsung Email app versions prior to 6.1.41.0 contain an Insecure Direct Object Reference (IDOR) vulnerability where attachment indices are predictable. This allows remote attackers to manipulate the index to access attachments from other emails when a user opens a malicious attachment.

MitigationUpdate Samsung Email to version 6.1.41.0 or later. Organizations should inventory devices running vulnerable versions and ensure the patch is applied.

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
EmailApplication
Affected:< 6.1.14.0

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Samsung Email app is installed
    Open device Settings > Apps > Application Manager, then search for 'Samsung Email' or navigate to Samsung folder and check if Email app exists
    Affected if Samsung Email app is present on the device
  2. Locate the installed version number
    In Settings > Apps > Samsung Email, view the App info screen and note the version number displayed under 'Version' or 'Version info'
    Affected if A version number is displayed (proceeds to version comparison)
  3. Compare version to affected range
    Compare your installed version number to 6.1.14.0 - the affected range is any version lower than 6.1.14.0
    Affected if Installed version is less than 6.1.14.0 (e.g., 6.1.13.5, 6.0.20, etc.)
  4. Check if Email sync is enabled
    Open Samsung Email app, go to Settings > Account settings, verify at least one email account is configured and syncing
    Affected if Email account is active and receiving emails with attachments

Device is affected if Samsung Email app is installed with version lower than 6.1.14.0 and the app is used to access emails with attachments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.1.14.0 or later
Fixed in 6.1.14.0
Interim mitigation

Update Samsung Email to version 6.1.41.0 or later. Organizations should inventory devices running vulnerable versions and ensure the patch is applied.

Fix this in Email Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-25375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-25375 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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