CVE-2025-20972
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 verification of intent by broadcast receiver in Samsung Flow prior to version 4.9.17.6 allows local attackers to modify Samsung Flow configuration.
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 confidenceSamsung Flow contains a broadcast receiver that does not properly verify the intent source before processing configuration changes. A local attacker can send a crafted broadcast to modify Samsung Flow settings without proper authentication, potentially altering security-relevant configuration parameters.
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< 4.9.17.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Samsung Flow is installedOn the Android device, go to Settings > Apps > Samsung Flow, or use adb command: adb shell pm list packages | grep samsung.flowAffected if Samsung Flow package (com.samsung.android.app.smartpanel) is present on the device
-
Retrieve the installed version of Samsung FlowNavigate to Samsung Flow in Settings > Apps > App info, or use adb: adb shell dumpsys package com.samsung.android.app.smartpanel | grep versionNameAffected if Unable to retrieve version information, indicating the app may not be properly installed
-
Compare installed version against the vulnerable rangeCheck if the version number is lower than 4.9.17.6. The version format typically appears as X.X.X.X in the app info screen or dumpsys output.Affected if Installed version is less than 4.9.17.6 (for example, 4.9.17.5, 4.9.16.3, or any earlier version)
-
Verify the broadcast receiver is presentUse adb to inspect the app manifest: adb shell dumpsys package com.samsung.android.app.smartpanel | grep -i broadcastreceiverAffected if The broadcast receiver component exists (this is the default state for the vulnerable versions)
The device is affected if Samsung Flow is installed with a version lower than 4.9.17.6, as the vulnerable broadcast receiver is present by default in these versions.
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.
dbcve · scoped4.9.17.6
Update Samsung Flow to version 4.9.17.6 or later via the Samsung Galaxy Store or Google Play Store. Organizations should push the update through their mobile device management (MDM) solutions to ensure all managed devices are patched.
4.9.17.6
- Open Galaxy Store or Google Play Store on your Samsung device
- Search for Samsung Flow
- Update Samsung Flow to version 4.9.17.6 or later
- Verify the installed version in app settings after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20972 — 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-2025-20972 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