CVE-2022-30717
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 caller check in AR Emoji prior to SMR Jun-2022 Release 1 allows untrusted applications to use some camera functions via deeplink.
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 confidenceImproper caller check in Samsung's AR Emoji feature allows untrusted applications to bypass authorization and invoke certain camera functions through a deeplink mechanism. This authorization bypass enables malicious apps to access camera functionality they should not have permission to use.
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= 10.0= 11.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 device is a Samsung modelCheck the device manufacturer by running 'getprop ro.product.manufacturer' or checking device settings. This vulnerability affects Samsung devices specifically.Affected if Device is not a Samsung product (the flaw is in Samsung's AR Emoji component)
-
Confirm Android version is 10.0 or 11.0Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Compare against the affected versions 10.0 and 11.0.Affected if Android version is 10.0 or 11.0 exactly (these are the affected versions)
-
Check if AR Emoji feature is presentLook for the AR Emoji package by running 'pm list packages | grep aremoji' or 'pm list packages | grep aremoji'. The package name is typically 'com.samsung.android.aremoji' or similar.Affected if AR Emoji package is installed on the device
-
Verify Samsung software patch levelCheck Settings > About Phone > Software information > Build number or run 'getprop ro.build.version.sem' to determine the SMR (Samsung Maintenance Release) version.Affected if SMR is earlier than Jun-2022 Release 1 (the patch was released in Jun-2022)
A user is affected if they have a Samsung device running Android 10.0 or 11.0 with the AR Emoji feature installed and an SMR version earlier than Jun-2022 Release 1.
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 · scopedUpdate Samsung devices to SMR Jun-2022 Release 1 or later to obtain the proper caller validation fix for the AR Emoji component.
SMR Jun-2022 Release 1 or later (Samsung Maintenance Release)
- Navigate to Settings on the Samsung device
- Scroll down and tap on 'Software update'
- Tap on 'Download and install' to check for and apply the latest Samsung security update
- Ensure the installed SMR (Samsung Maintenance Release) is June-2022 Release 1 or later
- Alternatively, check the Samsung Security Bulletin at security.samsungmobile.com for the specific patch version corresponding to CVE-2022-30717
- After updating, verify the camera permissions for AR Emoji are properly restricted in Settings > Apps > AR Emoji
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30717 — 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-30717 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