CVE-2024-38425
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 · uneditedInformation disclosure while sending implicit broadcast containing APP launch 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 an Android information disclosure vulnerability where an implicit broadcast is being sent containing application launch information. Implicit broadcasts can be intercepted by any application listening for that broadcast action, potentially exposing sensitive information about which apps are being launched to unauthorized observers.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 the Qualcomm chipset in the deviceRun 'getprop' command or check /system/build.prop for ro.board.platform or ro.product.board to determine the Qualcomm component modelAffected if The chipset matches Wsa8835, Wsa8830, Wcd9380, Snapdragon 8+ Gen 2, Snapdragon 8+ Gen 1, Snapdragon 8 Gen 3, Snapdragon 8 Gen 2, or Snapdragon 8 Gen 1
-
Check the firmware version of the Qualcomm componentQuery the device-specific firmware version through vendor-specific getprop entries (such as vendor.qcom.version.*) or check /vendor/firmware/ for the relevant component firmware filesAffected if Any firmware version is present (all versions of the affected products are vulnerable)
-
Monitor for implicit broadcasts containing app launch informationUse 'dumpsys activity broadcasts' or 'logcat' to observe system broadcasts with actions like ACTION_PACKAGE_ADDED, ACTION_PACKAGE_REPLACED, or similar package-related broadcasts. Filter for broadcasts that include app names or package information in their extrasAffected if Implicit broadcasts (broadcasts without a specified target component) are observed containing package names, app launch times, or other app launch metadata in the broadcast extras
If the device contains any of the listed Qualcomm chipsets and the system is sending implicit broadcasts with application launch information, the environment is affected by this vulnerability.
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.
From vendor dataConvert the implicit broadcast to an explicit broadcast (specifying the target component) or implement proper broadcast permissions to restrict reception to authorized components only. Avoid including sensitive app launch information in broadcast extras.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38425 — 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-38425 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