CVE-2022-30737
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 · uneditedImplicit Intent hijacking vulnerability in Samsung Account prior to version 13.2.00.6 allows attackers to get email ID.
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 an Android implicit Intent hijacking vulnerability in the Samsung Account app. The app likely broadcasts sensitive information (email ID) via implicit Intents without specifying a target package, allowing any malicious app on the device to register a BroadcastReceiver and intercept this sensitive data.
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< 13.2.00.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Samsung Account app versionOpen Settings > Apps > Samsung Account, then view the Version information. Alternatively, run: adb shell dumpsys package com.samsung.android.account.aas | grep versionNameAffected if The displayed version is less than 13.2.00.6
-
Verify package name is correctConfirm the app package name matches Samsung Account (com.samsung.android.account.aas or com.osp.app.signin). Use: adb shell pm list packages samsungAffected if Package name is not as expected for Samsung Account
-
Confirm the vulnerability is present by versionCompare your installed version number to the affected range: any version below 13.2.00.6 is affected by this implicit Intent hijacking flawAffected if Version is 13.2.00.5 or lower, meaning the app broadcasts email ID via implicit Intents without target package specification
You are affected if the installed Samsung Account version is lower than 13.2.00.6, as only versions prior to this contain the implicit Intent vulnerability that allows interception of email ID data.
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 · scoped13.2.00.6
Update Samsung Account to version 13.2.00.6 or later, which presumably implements explicit Intents or adds package verification to prevent unauthorized interception of the email ID data.
13.2.00.6
- Open the Google Play Store or Samsung Galaxy Store on your device
- Search for 'Samsung Account' or locate it in your installed apps
- Check the current version of Samsung Account installed on your device
- If the installed version is lower than 13.2.00.6, update the application to version 13.2.00.6 or later
- Alternatively, enable automatic app updates in your device settings to ensure you receive the latest secure version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30737 — 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-30737 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