dbcve.org
Galaxy Watch PluginPlugin / extension · Samsung

CVE-2022-36875

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 2.2.11.22081151 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
Improper restriction of broadcasting Intent in SaWebViewRelayActivity of?Waterplugin prior to version 2.2.11.22081151 allows attacker to access the file without permission.

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

Improper restriction of broadcasting Intent in SaWebViewRelayActivity of the Waterplugin Android component allows unauthorized file access without proper permission validation. This is an Intent handling vulnerability where broadcast actions can be intercepted or triggered by external malicious applications, leading to information disclosure or unauthorized file system access.

MitigationUpgrade Waterplugin to version 2.2.11.22081151 or later which contains the security fix. Additionally, implement proper permission checks and use local broadcasts or explicit intents with appropriate permission requirements for the SaWebViewRelayActivity component.

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
Galaxy Watch PluginPlugin / extension
Affected:< 2.2.11.22081151

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. Identify if Samsung Galaxy Watch Plugin is installed
    Run 'pm list packages | grep -i waterplugin' or 'pm list packages | grep -i galaxy' on the Android device to list installed packages related to Waterplugin or Galaxy Watch
    Affected if No Samsung Galaxy Watch Plugin (waterplugin) package is found, then the device is not affected by this specific vulnerability
  2. Retrieve the Waterplugin package version
    Execute 'dumpsys package <package_name>' replacing <package_name> with the identified Waterplugin package (e.g., com.samsung.android.waterplugin), then locate the 'versionName' or 'versionCode' field in the output
    Affected if The displayed version is lower than 2.2.11.22081151 (e.g., 2.2.10.x or earlier)
  3. Verify if SaWebViewRelayActivity is exported
    Run 'dumpsys package <package_name> | grep -A 10 SaWebViewRelayActivity' to examine the component declaration, looking for 'android:exported=true' in the activity configuration
    Affected if The activity shows android:exported="true" without proper permission requirements (android:permission attribute)
  4. Inspect broadcast receiver configurations
    Use 'aapt dump badging <apk_path>' or analyze the AndroidManifest.xml of the Waterplugin APK to check for broadcast receivers associated with SaWebViewRelayActivity and their permission constraints
    Affected if Broadcast receivers lack android:permission restrictions or use unprotected intent filters that external apps can intercept

The environment is affected if Samsung Galaxy Watch Plugin with Waterplugin is installed and its version is below 2.2.11.22081151, with the SaWebViewRelayActivity component exported without proper permission checks.

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

Upgrade Waterplugin to version 2.2.11.22081151 or later which contains the security fix. Additionally, implement proper permission checks and use local broadcasts or explicit intents with appropriate permission requirements for the SaWebViewRelayActivity component.

Recommended fix High confidence

Galaxy Watch Plugin version 2.2.11.22081151 or later

  1. Open the Galaxy Wearable app on your connected smartphone
  2. Navigate to the Galaxy Watch Plugin (or Waterplugin) settings
  3. Check the current installed version under 'About plugin' or 'Version'
  4. Update the plugin to version 2.2.11.22081151 or later via the Galaxy Wearable app or Samsung Galaxy Store
  5. Verify the update was successful by confirming the version number matches 2.2.11.22081151 or higher

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

Fix this in Galaxy Watch Plugin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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