dbcve.org
Wear OsOperating system · Samsung

CVE-2025-20912

MEDIUM · 6.2 CVSS v3.1 Published 2025-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges 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
Incorrect default permission in DiagMonAgent prior to SMR Mar-2025 Release 1 allows local attackers to access data within Galaxy Watch.

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

DiagMonAgent, a diagnostic monitoring component in Samsung Galaxy Watch devices, shipped with overly permissive default file or service permissions prior to the SMR Mar-2025 Release 1. This allows a local attacker with standard user privileges to potentially read sensitive diagnostic data or interact with the diagnostic service beyond intended boundaries.

MitigationApply the SMR Mar-2025 Release 1 firmware update to Galaxy Watch devices to obtain the corrected default permission configuration for DiagMonAgent.

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
Wear OsOperating system
Affected:= 5.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/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. Check the Wear OS version
    Navigate to Settings > About Watch on the Galaxy Watch device, or use ADB command: `adb shell getprop ro.build.version.release`
    Affected if The version displayed is 5.0 (exact match to affected version)
  2. Verify DiagMonAgent presence
    Check if the DiagMonAgent service is present on the device using ADB: `adb shell ps -A | grep -i DiagMonAgent` or list related files in system directories
    Affected if DiagMonAgent process or binary is found running on the device with Wear OS 5.0
  3. Inspect DiagMonAgent service permissions
    Use ADB to check service permissions: `adb shell dumpsys service DiagMonAgent` and examine the permission settings, or check file permissions with `adb shell ls -la /path/to/DiagMonAgent`
    Affected if The service or its associated files show world-readable/writeable permissions or overly permissive access control (e.g., permission level set to 'normal' or 'dangerous' without proper restrictions)
  4. Check diagnostic data access controls
    Examine whether standard user apps can access DiagMonAgent-related diagnostic data or interfaces by attempting to query the service from a non-privileged context: `adb shell appops get <package> DiagMonAgent`
    Affected if Non-privileged applications have access to invoke or interact with the DiagMonAgent service beyond intended boundaries

A user is affected if their Galaxy Watch runs Wear OS version 5.0 and the DiagMonAgent component has overly permissive file or service permissions that allow standard user access to sensitive diagnostic 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SMR Mar-2025 Release 1 firmware update to Galaxy Watch devices to obtain the corrected default permission configuration for DiagMonAgent.

Recommended fix High confidence

SMR Mar-2025 Release 1 (or later) for Wear OS 5.0 Galaxy Watch devices

  1. Check the current SMR version on the Galaxy Watch device via Settings > About Watch > Software Information
  2. Navigate to Settings > Software Update on the Galaxy Watch
  3. Select 'Download and Install' to check for and apply the latest available update
  4. Ensure the update reaches SMR Mar-2025 Release 1 or later which contains the DiagMonAgent permission fix
  5. Verify the update was successfully installed by checking the SMR version again in About Watch > Software Information
Caveat Standard Wear OS update considerations apply - ensure device is charged and connected to stable Wi-Fi before updating

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

Fix this in Wear Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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