dbcve.org
Samsung EmailApplication · Samsung

CVE-2022-36837

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 6.1.70.20 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Intent redirection vulnerability using implicit intent in Samsung email prior to version 6.1.70.20 allows attacker to get sensitive information.

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

This is an intent redirection vulnerability in the Samsung email Android application. The app uses implicit intents (which don't specify a target component) when handling sensitive data, allowing a malicious app installed on the same device to intercept or redirect these intents and access sensitive information such as email credentials or content.

MitigationUpdate Samsung email app to version 6.1.70.20 or later which contains the fix; alternatively, minimize risk by not installing apps from untrusted sources and revoking unnecessary permissions from third-party apps.

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
Samsung EmailApplication
Affected:< 6.1.70.20

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 Settings > Apps > Samsung Email, or run: adb shell pm list packages | grep -i email
    Affected if Package name com.samsung.android.email.provider is present on device
  2. Check installed Samsung Email version
    Navigate to Settings > Apps > Samsung Email > App info > Version, or run: adb shell pm dump com.samsung.android.email.provider | grep versionName
    Affected if Version number displayed is lower than 6.1.70.20 or version name cannot be retrieved (app is outdated)
  3. Confirm intent handling vulnerability is present
    Review app permissions in Settings > Apps > Samsung Email > Permissions. The vulnerability exists if the app sends implicit intents containing sensitive data (email credentials, attachments) without specifying explicit target components
    Affected if Samsung Email version is below 6.1.70.20 AND the app has permissions for network access, contacts, or storage (common for email functionality)
  4. Check for presence of malicious apps with intent interception capabilities
    Review installed apps in Settings > Apps. Look for unknown or untrusted apps requesting activity or broadcast receiver permissions, especially those with permission to intercept intents
    Affected if Unknown third-party apps with broad permission sets are installed alongside vulnerable Samsung Email version

User is affected if Samsung Email version is below 6.1.70.20 and the app handles sensitive email data using implicit intents on a device that may contain untrusted third-party apps.

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.

dbcve · scoped
Upgrade available Upgrade to 6.1.70.20 or later
Fixed in 6.1.70.20
Interim mitigation

Update Samsung email app to version 6.1.70.20 or later which contains the fix; alternatively, minimize risk by not installing apps from untrusted sources and revoking unnecessary permissions from third-party apps.

Recommended fix High confidence

Samsung Email version 6.1.70.20 or later

  1. Open the Google Play Store (or Samsung Galaxy Store) on the device
  2. Search for 'Samsung Email' or locate it in your installed apps
  3. Tap the Update button to install the latest version
  4. Verify the installed version is 6.1.70.20 or later via App Info > Version
Caveat Minimal risk - routine security update for Samsung Email app; ensure device OS is compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Samsung Email Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36837 — 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-2022-36837 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