CVE-2022-28776
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 · uneditedImproper access control vulnerability in Galaxy Store prior to version 4.5.36.4 allows attacker to install applications from Galaxy Store without user interactions.
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 confidenceAn improper access control vulnerability in Samsung Galaxy Store versions prior to 4.5.36.4 allows a remote or local attacker to bypass user interaction requirements and install applications from the Galaxy Store without the user's consent. This bypass of authentication/authorization controls enables unauthorized app installation.
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< 4.5.36.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Galaxy Store installationOpen Android Settings > Apps > Galaxy Store, or use ADB command: pm list packages | grep samsung.apps.storeAffected if The Galaxy Store package (com.sec.android.app.samsungapps) is present on the device
-
Check installed Galaxy Store versionIn Settings > Apps > Galaxy Store, view the Version information displayed under the app name, or use ADB command: dumpsys package com.sec.android.app.samsungapps | grep versionNameAffected if A version number is displayed that is lower than 4.5.36.4 (for example: 4.5.35.8, 4.5.30.2, etc.)
-
Verify the exact version stringCompare your extracted version against the vulnerable threshold: any version below 4.5.36.4 is affected. Version 4.5.36.4 and later are patched.Affected if The version shown is below 4.5.36.4 (the affected range is any version prior to 4.5.36.4)
If Samsung Galaxy Store is installed and its version is below 4.5.36.4, the device is affected by this vulnerability and could allow unauthorized app installation without user interaction.
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 · scoped4.5.36.4
Update Galaxy Store to version 4.5.36.4 or later to remediate this vulnerability. Organizations should audit managed mobile devices to ensure the vulnerable version is not present.
Galaxy Store version 4.5.36.4 or later
- Open the Galaxy Store app on your Samsung device
- Navigate to the settings or menu options
- Check for updates or ensure auto-update is enabled
- Update Galaxy Store to version 4.5.36.4 or later
- Verify the updated version in the app settings after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28776 — 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-2022-28776 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