CVE-2022-36873
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 restriction of broadcasting Intent in GalaxyStoreBridgePageLinker of?Waterplugin prior to version 2.2.11.22081151 leaks MAC address of the connected Bluetooth device.
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 confidenceImproper restriction of broadcasting Intent in GalaxyStoreBridgePageLinker of Waterplugin allows a malicious application to receive Intent broadcasts containing the MAC address of a connected Bluetooth device. The component broadcasts sensitive Bluetooth device information without proper access controls, enabling unauthorized apps to intercept this information.
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< 2.2.11.22081151CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Samsung Galaxy Watch Plugin is installedCheck device settings under Apps or use package manager command to list installed applications. Look for 'Samsung Galaxy Watch Plugin' or related Waterplugin component.Affected if The application is present on the device
-
Check installed version of Samsung Galaxy Watch PluginIn device Settings > Apps > Samsung Galaxy Watch Plugin, view the version information. Compare the version code to 2.2.11.22081151. Versions below this number are affected.Affected if Installed version is less than 2.2.11.22081151
-
Verify the GalaxyStoreBridgePageLinker component existsUse Android debugging tools or analyze the app APK to check for the presence of the GalaxyStoreBridgePageLinker component within the Waterplugin package.Affected if The GalaxyStoreBridgePageLinker component is present in the application
A user is affected if Samsung Galaxy Watch Plugin with Waterplugin is installed and the version is below 2.2.11.22081151, allowing unauthorized apps to receive Bluetooth MAC addresses via unrestricted Intent broadcasts.
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 · scoped2.2.11.22081151
Upgrade Waterplugin to version 2.2.11.22081151 or later. If upgrade is not possible, restrict Intent broadcasts to only intended receivers by using explicit Intents, setPackage(), or implementing proper permission checks on receivers.
2.2.11.22081151
- Open the Galaxy Wearable app or Galaxy Watch Plugin on your smartphone
- Navigate to Settings or the About section
- Check the current plugin version to confirm it's below 2.2.11.22081151
- Access your device's app store (Google Play Store or Galaxy Store)
- Search for Galaxy Watch Plugin or check for updates within the Galaxy Wearable app
- Update to version 2.2.11.22081151 or later
- Verify the update was successful by checking the version number again
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-2022-36873 — 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-2022-36873 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