dbcve.org
AndroidOperating system · Google

CVE-2022-30755

HIGH · 7.8 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper authentication vulnerability in AppLock prior to SMR Jul-2022 Release 1 allows attacker to bypass password confirm activity by hijacking the implicit intent.

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 confidence

Improper authentication in Samsung AppLock allows bypassing the password confirmation activity by hijacking an implicit intent. This is a vulnerability in the authentication flow where intent handling is not properly secured, allowing an attacker to circumvent the password check.

MitigationApply the Samsung SMR July-2022 Release 1 or later security update to receive the patched AppLock version.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Android version
    Go to Settings > About Phone > Android version or use 'adb shell getprop ro.build.version.release'
    Affected if The device runs Android 10.0, 11.0, or 12.0 (exact match to 10.0, 11.0, or 12.0)
  2. Locate Samsung AppLock application
    Check if Samsung AppLock (package name typically 'com.samsung.android.applock') is installed by navigating to Settings > Apps > AppLock or using 'adb shell pm list packages | findstr applock'
    Affected if Samsung AppLock is installed on the device
  3. Check AppLock version
    Open Galaxy Store or Play Store and check for Samsung AppLock updates, or navigate to Settings > Apps > AppLock > App info to view the installed version
    Affected if The installed AppLock version is older than the July 2022 security update (patched version unknown, compare against update release date)
  4. Verify intent handling configuration
    Review AppLock permissions and intent filters using 'adb shell dumpsys package com.samsung.android.applock' and check for exposed implicit intents in the authentication flow
    Affected if Implicit intents in password confirmation activity are not properly secured or protected
  5. Confirm device vendor and model
    Verify the device is a Samsung device by checking 'adb shell getprop ro.product.brand' or checking the device model in Settings > About Phone
    Affected if The device is a Samsung device running affected Android versions with AppLock installed

A user is affected if running Android 10.0, 11.0, or 12.0 on a Samsung device with Samsung AppLock installed and the AppLock version predates the July 2022 security patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Samsung SMR July-2022 Release 1 or later security update to receive the patched AppLock version.

Recommended fix High confidence

SMR Jul-2022 Release 1 (or later)

  1. Open Settings on the Samsung device
  2. Navigate to 'Software update' or 'System updates'
  3. Tap 'Download and install' to check for available updates
  4. If SMR Jul-2022 Release 1 or later is available, download and install the update
  5. Verify the update was applied by checking the Android security patch level in Settings > About phone > Software information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30755 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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