dbcve.org
Dynamic LockscreenApplication · Samsung

CVE-2022-39862

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-07
Fix available
A fix is available. Upgrade to 3.3.03.66 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 authorization in Dynamic Lockscreen prior to SMR Sep-2022 Release 1 in Android R(11) and 3.3.03.66 in Android S(12) allows unauthorized use of javascript interface api.

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

This is a Samsung Android vulnerability in the Dynamic Lockscreen component where improper authorization controls allow unauthorized access to the javascript interface API. An attacker with local or physical access could potentially exploit this to execute privileged operations through the lockscreen without proper authentication. The vulnerability affects Android R (11) and S (12) devices running Dynamic Lockscreen versions prior to SMR Sep-2022 Release 1 and 3.3.03.66 respectively.

MitigationApply the Samsung September 2022 security update (SMR) which patches Dynamic Lockscreen to version 3.3.03.66 or later, or as otherwise provided by Samsung for the specific device model.

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
Dynamic LockscreenApplication
Affected:< 3.3.03.66

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 if Dynamic Lockscreen is installed
    Run 'adb shell pm list packages | grep -i cocktail' or check app settings for a Samsung app named 'Dynamic Lock' or 'CocktailProv'
    Affected if The Dynamic Lockscreen package is not present on the device (not vulnerable as the component is not installed)
  2. Determine the Dynamic Lockscreen version
    Run 'adb shell dumpsys package com.samsung.android.app.cocktailprovs' and look for versionName or versionCode, or check the app info in Settings > Apps > Dynamic Lockscreen
    Affected if The installed version is below 3.3.03.66 (compare versionName or convert versionCode to determine if it is less than 303036600)
  3. Confirm Android OS version is R or S
    Run 'adb shell getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Android version is 11 (R) or 12 (S); devices on Android 13 or later are not in the affected range per the advisory
  4. Verify javascript interface API exposure
    Inspect Dynamic Lockscreen app permissions via 'adb shell dumpsys package com.samsung.android.app.cocktailprovs' and check if the app has INTERFACE permission exposed, or use a security tool to check if the javascript bridge is accessible from the lockscreen
    Affected if The javascript interface API is accessible without proper authorization checks (this requires dynamic analysis or code review to confirm)

A device is affected if it runs Android 11 or 12, has the Dynamic Lockscreen app installed, and the installed version is below 3.3.03.66, allowing unauthorized access to privileged operations through the lockscreen javascript interface.

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
Upgrade available Upgrade to 3.3.03.66 or later
Fixed in 3.3.03.66
Interim mitigation

Apply the Samsung September 2022 security update (SMR) which patches Dynamic Lockscreen to version 3.3.03.66 or later, or as otherwise provided by Samsung for the specific device model.

Recommended fix High confidence

Dynamic Lockscreen version 3.3.03.66 (SMR Sep-2022 Release 1)

  1. Open the Galaxy Store app on your Samsung device
  2. Search for 'Dynamic Lockscreen' or navigate to your installed apps
  3. Tap Update to install the latest version, or ensure auto-update is enabled
  4. Alternatively, check for system updates via Settings > Software update > Download and install to receive the SMR Sep-2022 Release 1 patch
  5. Verify the installed version is 3.3.03.66 or later in Settings > Apps > Dynamic Lockscreen > App info

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

Fix this in Dynamic Lockscreen Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39862 — 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-39862 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