CVE-2024-34680
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 · uneditedUse of implicit intent for sensitive communication in WlanTest prior to SMR Nov-2024 Release 1 allows local attackers to get sensitive information.
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 confidenceThis is a Samsung Android vulnerability in the WlanTest component where implicit intents are used to transmit sensitive information. Implicit intents in Android don't specify a target component, allowing any application to intercept them, enabling a local attacker to receive sensitive WiFi-related data without user consent.
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= 12.0= 13.0= 14.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Samsung device manufacturerRun 'getprop ro.product.manufacturer' in ADB shell or check Settings > About Phone > ManufacturerAffected if Manufacturer is not Samsung (not affected)
-
Check Android versionRun 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android versionAffected if Version is 12.0, 13.0, or 14.0 (matches affected versions)
-
Identify WlanTest componentRun 'pm list packages | grep -i wlan' or 'dumpsys package' to list packages containing 'wlan' in the package nameAffected if WlanTest or similar WiFi testing component is installed on the device
Device is affected if it is a Samsung Android device running version 12.0, 13.0, or 14.0 with the WlanTest component present and handling implicit intents for WiFi data
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 · scopedApply the Samsung SMR Nov-2024 Release 1 or later firmware update to affected devices to resolve the implicit intent issue.
SMR Nov-2024 Release 1 or later
- Identify the Samsung device model and verify it is running Android 12, 13, or 14
- Navigate to Settings > Security and privacy > Security update on the Samsung device
- Check for and install the Samsung Security Maintenance Release (SMR) November 2024 or later update
- Verify the update was successfully installed by checking the security patch date in Settings > About phone > Software information
- Ensure the device shows a security patch level of November 2024 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34680 — 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-2024-34680 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