dbcve.org
Galaxy StoreApplication · Samsung

CVE-2024-20825

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 IAP 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 In-App Purchase (IAP) module of Samsung's Galaxy Store. Android implicit intents can be intercepted by malicious local applications if not properly secured, allowing attackers to capture sensitive IAP-related data intended for the legitimate Galaxy Store component.

MitigationUpdate Galaxy Store to version 4.5.63.6 or later. Organizations with custom IAP implementations should review intent handling and use explicit intents instead of implicit ones for sensitive operations.

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. Locate the Galaxy Store app on the Android device
    Open the device Settings, then navigate to Apps or Applications, and search for 'Galaxy Store' in the list of installed applications
    Affected if Galaxy Store is not installed on the device, then this CVE does not apply
  2. Identify the installed Galaxy Store version number
    In Settings > Apps > Galaxy Store, view the 'Version' or 'App version' information displayed under the app name. Alternatively, open Galaxy Store, tap the menu (three horizontal lines), select Settings, then About to view version details
    Affected if Unable to determine the version indicates Galaxy Store may not be present or accessible for inspection
  3. Compare the installed version against the vulnerable range
    Take the version number identified (for example, 4.5.63.5 or earlier) and compare it numerically to 4.5.63.6. Any version lower than 4.5.63.6 falls within the affected range
    Affected if Installed version is less than 4.5.63.6 (for example, 4.5.63.5, 4.5.62.0, or any 4.x version below 4.5.63.6)
  4. Verify IAP functionality is in use
    Check if any applications on the device use Samsung's In-App Purchase (IAP) API or if Galaxy Store is used for purchasing apps, games, or digital content. This can be confirmed by reviewing installed apps that offer paid content or by checking Galaxy Store purchase history
    Affected if IAP functionality is actively used and Galaxy Store version is below 4.5.63.6, making the implicit intent hijacking exploitable

The device is affected if Samsung Galaxy Store is installed with a version number less than 4.5.63.6 and the device or any installed apps utilize the In-App Purchase functionality.

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. Organizations with custom IAP implementations should review intent handling and use explicit intents instead of implicit ones for sensitive operations.

Recommended fix High confidence

Galaxy Store version 4.5.63.6 or later

  1. Open the Galaxy Store app on the Samsung device
  2. Tap the menu icon (three lines or hamburger menu) in the top-left corner
  3. Tap 'Settings' or 'Galaxy Store version'
  4. Tap 'Update' or check for available updates
  5. If an update is available, download and install version 4.5.63.6 or later
  6. Alternatively, open Galaxy Store and navigate to Updates section to check for and apply the latest version

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

Fix this in Galaxy Store Scoped from the published advisory
  • Consultation2.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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-20825 — 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-20825 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