CVE-2022-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 · uneditedUnprotected component vulnerability in DeviceSearchTrampoline in SecSettingsIntelligence prior to SMR Jun-2022 Release 1 allows local attackers to launch activities of SecSettingsIntelligence.
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 confidenceThe DeviceSearchTrampoline component in Samsung's SecSettingsIntelligence app is improperly exported without permission protection, allowing any local application to launch its activities. This enables a local attacker to potentially access sensitive settings functionality that should be restricted.
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= 12.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
- 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.
-
Verify Android version is 12.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device is running Android 12.0 specifically
-
Check if SecSettingsIntelligence app is installedRun 'pm list packages | grep SecSettingsIntelligence' via ADB shell, or check in Settings > AppsAffected if The SecSettingsIntelligence package is present on the device
-
Inspect the DeviceSearchTrampoline component export statusRun 'dumpsys package com.samsung.android.app.secsettingsintelligence' via ADB shell and look for DeviceSearchTrampoline in the exported componentsAffected if DeviceSearchTrampoline is listed as exported without requiring a signature permission (android:permission attribute is missing or unset)
-
Verify the component lacks permission protectionParse the dumpsys output to confirm the component has no android:permission or android:exported="false" attribute setAffected if The component accepts intents from any application without signature-level permission validation
The device is affected if running Android 12.0 with SecSettingsIntelligence installed and the DeviceSearchTrampoline component is exported without signature-level permission protection.
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 to SMR Jun-2022 Release 1 or later, which implements proper permission protection on the DeviceSearchTrampoline component by setting appropriate android:exported and android:permission attributes in the AndroidManifest.xml.
SMR Jun-2022 Release 1 (Android Security Patch Level June 2022)
- Go to Settings on the Samsung device
- Navigate to About Phone or Software Update
- Check the current Android security patch level
- Select Check for Updates or Download updates manually
- Download and install the SMR Jun-2022 Release 1 security update which includes the fix for CVE-2022-30726
- Verify the device now shows the June 2022 security patch level after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-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-2022-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