CVE-2023-30726
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 · uneditedPendingIntent hijacking vulnerability in GameLauncher prior to version 4.2.59.5 allows local attackers to access data.
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 a PendingIntent hijacking vulnerability in the GameLauncher Android application. PendingIntent allows an app to pass a future intent to another app; when not properly secured (missing FLAG_EXCLUDE_CURRENT or lacking explicit component names), a local malicious app can intercept or manipulate these intents, enabling unauthorized data access.
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.2.59.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GameLauncher is installedCheck if the com.samsung.android.game.gamehome package exists on the device using 'adb shell pm list packages | grep gamehome' or via Settings > Apps on the deviceAffected if GameLauncher package is not present on the device (not vulnerable because app is not installed)
-
Retrieve installed GameLauncher versionRun 'adb shell dumpsys package com.samsung.android.game.gamehome | grep versionName' or check the app version in Settings > Apps > GameLauncher > App infoAffected if Unable to determine version (app may be corrupted or hidden)
-
Compare version to affected rangeCompare the retrieved version number against the affected range: any version below 4.2.59.5 is vulnerable. For example, if version shows 4.2.58.3 or 4.1.04.2, it falls within the affected rangeAffected if Version is less than 4.2.59.5 (for example, 4.2.59.4, 4.2.58.0, 4.1.00.5, etc.)
-
Verify device is SamsungConfirm the device manufacturer is Samsung by checking 'adb shell getprop ro.product.brand' or the device Settings > About phoneAffected if Device is not a Samsung device - GameLauncher may not be the official vulnerable version or may not be present
User is affected if GameLauncher (com.samsung.android.game.gamehome) is installed on a Samsung device and its version is below 4.2.59.5
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.2.59.5
Update GameLauncher to version 4.2.59.5 or later, which contains the fix for the insecure PendingIntent handling. If update is not possible, audit code for PendingIntent creation and ensure FLAG_EXCLUDE_CURRENT is used with explicit intents.
4.2.59.5
- Open the Galaxy Store app on your Samsung device
- Search for "GameLauncher" or "Game Tools"
- Check if an update is available for the application
- If an update is available, tap Update to install version 4.2.59.5 or later
- Alternatively, ensure your Samsung device's system software is up to date, as GameLauncher updates may be included in system updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30726 — 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-2023-30726 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