Galaxy StoreApplication · Samsung

CVE-2024-20824

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to 4.5.63.6 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Implicit intent hijacking vulnerability in VoiceSearch of Galaxy Store prior to version 4.5.63.6 allows local attackers to access sensitive information via implicit intent.

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

This is an implicit intent hijacking vulnerability in the VoiceSearch component of Samsung's Galaxy Store app. Android implicit intents can be intercepted by any app that declares a matching intent filter, allowing a malicious local app to receive sensitive data intended for VoiceSearch. The fix requires using explicit intents or properly validating the receiving component.

MitigationUpdate Galaxy Store to version 4.5.63.6 or later. Users should also be cautious about installing apps from unknown sources, as local attackers need an installed app to intercept intents.

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 StoreApplication
Affected:< 4.5.63.6

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Confirm Galaxy Store is installed
    Use 'adb shell pm list packages | grep samsungapps' or navigate to Settings > Apps on the Android device and look for Galaxy Store
    Affected if If the package com.sec.android.app.samsungapps is not present, the app is not installed and this CVE does not apply
  2. Retrieve the Galaxy Store version number
    Run 'adb shell dumpsys package com.sec.android.app.samsungapps | grep versionName' or go to Settings > Apps > Galaxy Store and read the version displayed under App info
    Affected if Unable to obtain a version number indicates the app may be corrupted or hidden
  3. Compare version against vulnerable range
    Take the version number obtained in step 2 and compare it numerically to 4.5.63.6 - note that version strings may be in format x.x.x.x so compare each segment
    Affected if The installed version is less than 4.5.63.6 (for example, 4.5.63.5 or any earlier version)
  4. Verify the VoiceSearch component exists
    Check if VoiceSearch functionality is available in Galaxy Store by opening the app and looking for a voice search icon or feature, or inspect the app manifest via 'adb shell dumpsys package com.sec.android.app.samsungapps' for VoiceSearch-related activities
    Affected if VoiceSearch component is not present or accessible means the specific attack surface may not exist

The environment is affected if Galaxy Store is installed with a version lower than 4.5.63.6 and the VoiceSearch component is present and functional.

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

Update Galaxy Store to version 4.5.63.6 or later. Users should also be cautious about installing apps from unknown sources, as local attackers need an installed app to intercept intents.

Recommended fix High confidence

Galaxy Store version 4.5.63.6 or later

  1. Open the Galaxy Store app on your Samsung device
  2. Navigate to the menu or settings within Galaxy Store
  3. Check for updates or go to the 'My Galaxy' section
  4. Update Galaxy Store to version 4.5.63.6 or later
  5. Verify the update was successful by checking the app version in settings

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

Fix this in Galaxy Store Scoped from the published advisory
  • Consultation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20824 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