dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-32670

HIGH · 7.0 CVSS v4.0 Published 2024-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
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
Exposure of Sensitive Information to an Unauthorized Actor in Samsung Galaxy SmartTag2 prior to 0.20.04 allows attackes to potentially identify the tag's location by scanning the BLE adversting.

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 confidence

The Samsung Galaxy SmartTag2 prior to version 0.20.04 exposes sensitive information through BLE (Bluetooth Low Energy) advertising packets. This BLE privacy flaw allows unauthorized nearby actors to scan and potentially track the device's location by intercepting these advertising transmissions.

MitigationUsers should update their Galaxy SmartTag2 firmware to version 0.20.04 or later through the Samsung SmartThings app to remediate the BLE advertising information exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate your Galaxy SmartTag2 device
    Open the Samsung SmartThings app and identify all registered Galaxy SmartTag2 devices in your device list
    Affected if a Galaxy SmartTag2 is present in your SmartThings account
  2. Check the firmware version
    In the SmartThings app, select each Galaxy SmartTag2 and navigate to Device Settings > Device Information to view the current firmware version
    Affected if the displayed firmware version is a numeric value less than 0.20.04
  3. Compare version to the affected range
    Compare your installed firmware version number against the affected range: any version prior to 0.20.04 is vulnerable
    Affected if the firmware version starts with 0.20.x but is less than 0.20.04, or begins with a lower major/minor such as 0.19.x, 0.18.x, etc.

If any Galaxy SmartTag2 in your SmartThings account runs firmware version 0.20.04 or higher, that specific device is not affected; all devices running versions below 0.20.04 are affected by this BLE advertising information exposure.

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

Users should update their Galaxy SmartTag2 firmware to version 0.20.04 or later through the Samsung SmartThings app to remediate the BLE advertising information exposure.

Recommended fix Moderate confidence

Firmware version 0.20.04 for Samsung Galaxy SmartTag2

  1. 1. Open the SmartThings app on your Samsung Galaxy device
  2. 2. Navigate to the Devices tab and select your Galaxy SmartTag2
  3. 3. Tap on the settings (three dots) menu for the SmartTag2
  4. 4. Look for firmware or software update option
  5. 5. Check for and install any available updates
  6. 6. Verify the firmware version is 0.20.04 or higher after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Review / QA1.0 h
2.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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