Galaxy StoreApplication · Samsung

CVE-2022-28542

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-11
Fix available
A fix is available. Upgrade to 4.5.40.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Improper sanitization of incoming intent in Galaxy Store prior to version 4.5.40.5 allows local attackers to access privileged content providers as Galaxy Store permission.

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

Improper sanitization of incoming Android intents in Galaxy Store versions prior to 4.5.40.5 allows a malicious local application to send crafted intents that the vulnerable app processes with its elevated permissions, enabling unauthorized access to privileged content providers.

MitigationUpdate Galaxy Store to version 4.5.40.5 or later on affected Samsung devices; for enterprise fleets, inventory vulnerable device models and enforce update via MDM or patch management.

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.40.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Galaxy Store is installed
    Use Android device settings or ADB command: 'pm list packages | grep com.sec.android.app.samsungapps' to see if the Samsung Galaxy Store package exists on the device
    Affected if Galaxy Store package (com.sec.android.app.samsungapps) is present on the device
  2. Retrieve installed Galaxy Store version
    Use ADB command: 'dumpsys package com.sec.android.app.samsungapps' and look for 'versionName' in the output, or check via Settings > Apps > Galaxy Store > Version on the device
    Affected if Unable to retrieve version information indicates the app may not be properly installed or accessible
  3. Compare version against affected range
    Compare the installed version number to 4.5.40.5 - any version prior to 4.5.40.5 (such as 4.5.x.x, 4.4.x.x, or earlier) is within the affected range
    Affected if Installed version is lower than 4.5.40.5 (for example, 4.5.38.3, 4.4.02.1, etc.)
  4. Verify intent handling exposure
    This vulnerability is exploitable when Galaxy Store runs with elevated system permissions and receives intents from other installed applications - confirm that other apps can send intents to the Galaxy Store component
    Affected if Galaxy Store is active and any third-party application can send broadcast intents to it without restriction

A device is affected if Samsung Galaxy Store is installed with a version number lower than 4.5.40.5, as that version introduced proper intent sanitization to prevent unauthorized access to privileged content providers.

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.40.5 or later
Fixed in 4.5.40.5
Interim mitigation

Update Galaxy Store to version 4.5.40.5 or later on affected Samsung devices; for enterprise fleets, inventory vulnerable device models and enforce update via MDM or patch management.

Recommended fix High confidence

Galaxy Store version 4.5.40.5 or higher

  1. Open the Galaxy Store app on the Samsung device
  2. Navigate to the menu (typically three lines or dots in the upper left corner)
  3. Select 'Settings' or 'My Apps'
  4. Check for updates or navigate to the updates section
  5. Update Galaxy Store to version 4.5.40.5 or later
  6. Alternatively, ensure automatic updates are enabled in Galaxy Store settings to receive future security updates

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
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2022-28542 — 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-2022-28542 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