CVE-2022-30748
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 · uneditedUnprotected dynamic receiver in Samsung Members prior to version 4.2.005 allows attacker to launch arbitrary activity.
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 confidenceSamsung Members app prior to version 4.2.005 contains an unprotected exported dynamic broadcast receiver. This allows any local application to send intents to this receiver, enabling an attacker to trigger the launch of arbitrary activities within the Samsung Members app context.
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.005CVSS 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.
-
Verify Samsung Members app is installedOn the device, go to Settings > Apps and search for Samsung Members, or run: adb shell pm list packages | grep samsung.memberAffected if The package com.samsung.android.app.members is present on the device
-
Check installed versionIn Settings > Apps > Samsung Members > App info, note the version number displayed, or run: adb shell dumpsys package com.samsung.android.app.members | grep versionNameAffected if The version shown is lower than 4.2.005
-
Confirm vulnerable receiver is exportedDecompile the APK and examine AndroidManifest.xml for dynamic broadcast receiver definitions, or run: adb shell dumpsys package com.samsung.android.app.members to inspect receiver configurationsAffected if A receiver has android:exported set to true without android:permission requirements
You are affected if Samsung Members app version is below 4.2.005 and the app contains an exported broadcast receiver accessible to other local applications.
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.005
Update Samsung Members to version 4.2.005 or later. If unable to update, apply appropriate permission protection to the dynamic receiver in the AndroidManifest.xml or disable its exported status if not required for external communication.
Samsung Members version 4.2.005
- Open the Galaxy Store or Google Play Store on the Samsung device
- Search for "Samsung Members" or locate the app in your app list
- Tap Update to install version 4.2.005 or later
- Verify the installed version is 4.2.005 or higher in the app settings or app info
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30748 — 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-30748 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