dbcve.org
Samsung FlowApplication · Samsung

CVE-2021-25507

MEDIUM · 5.7 CVSS v3.1 Published 2021-11-05
Fix available
A fix is available. Upgrade to 4.8.03.5 or later.
See remediation →
59/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
Improper authorization vulnerability in Samsung Flow mobile application prior to 4.8.03.5 allows Samsung Flow PC application connected with user device to access part of notification data in Secure Folder without authorization.

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 confidence

Samsung Flow mobile application prior to version 4.8.03.5 contains an improper authorization vulnerability that allows a connected Samsung Flow PC application to access certain notification data within the Secure Folder without performing proper authorization checks, exposing sensitive information to an authenticated but unauthorized entity.

MitigationUpdate Samsung Flow mobile application to version 4.8.03.5 or later to receive the vendor patch that enforces proper authorization before allowing PC applications to access Secure Folder notification data.

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 FlowApplication
Affected:< 4.8.03.5

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

CVSS:3.1/AV:A/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 Flow mobile app is installed
    Check the installed applications on the Android mobile device for Samsung Flow. This can be done via Settings > Apps > Samsung Flow, or by querying the package manager: `adb shell pm list packages | grep samsung.flow`
    Affected if Samsung Flow mobile application is present on the device
  2. Determine the installed version of Samsung Flow
    Open Samsung Flow app, go to Settings > About Flow, or check the version in Settings > Apps > Samsung Flow > App info. Compare the version number to 4.8.03.5
    Affected if The installed version is lower than 4.8.03.5
  3. Confirm Secure Folder is configured and active
    Check if Secure Folder is enabled on the device: go to Settings > Biometrics and security > Secure Folder, or look for the Secure Folder app icon in the app drawer
    Affected if Secure Folder is enabled and contains sensitive notifications
  4. Check for active Samsung Flow PC connection
    On the mobile device, open Samsung Flow and verify if any PC application is currently paired or connected. Check the connected devices list within the Samsung Flow app
    Affected if A Samsung Flow PC application is paired and connected to the mobile app

A user is affected if Samsung Flow mobile application version below 4.8.03.5 is installed, Secure Folder is active, and a PC application is connected, allowing unauthorized access to Secure Folder notification data.

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 4.8.03.5 or later
Fixed in 4.8.03.5
Interim mitigation

Update Samsung Flow mobile application to version 4.8.03.5 or later to receive the vendor patch that enforces proper authorization before allowing PC applications to access Secure Folder notification data.

Recommended fix High confidence

4.8.03.5

  1. Open Google Play Store or Samsung Galaxy Store on the mobile device
  2. Search for "Samsung Flow" in the app store
  3. Tap on Samsung Flow and select "Update" to install version 4.8.03.5 or later
  4. Alternatively, enable auto-updates for Samsung Flow in the app store settings to ensure future security updates are applied automatically
  5. Verify the update was successful by checking the app version in the device's app settings

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

Fix this in Samsung Flow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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