dbcve.org
AndroidOperating system · Google

CVE-2022-25832

MEDIUM · 6.8 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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 authentication vulnerability in S Secure prior to SMR Apr-2022 Release 1 allows physical attackers to use locked Myfiles app without authentication.

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 S Secure (prior to SMR Apr-2022 Release 1) allows a physical attacker to bypass lock screen authentication and access the Myfiles app without credentials. The vulnerability is exploitable by someone with physical access to the device.

MitigationApply the SMR Apr-2022 Release 1 security update to Samsung devices running S Secure. Organizations should ensure physical security controls are in place for devices until the update is deployed.

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

CVSS:3.1/AV:P/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. Verify Android version is 11.0 or 12.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version is 11.0 or 12.0 - these are the specifically listed affected versions
  2. Confirm S Secure application is installed
    Check for S Secure app in Settings > Apps, or list packages via ADB with 'pm list packages | grep samsung.credential'
    Affected if S Secure is present on the device - this is the vulnerable component
  3. Check S Secure version or build date
    Open S Secure app > Settings > About, or check via 'dumpsys package com.samsung.android.credentialmanager'
    Affected if Version or build date is prior to the SMR Apr-2022 Release 1 - this indicates the unpatched state
  4. Verify lock screen authentication is configured
    Check Settings > Lock screen > Screen lock type is set to PIN, pattern, or password
    Affected if Lock screen security is enabled - the bypass only matters when authentication is configured
  5. Test Myfiles app access without authentication
    With screen locked, attempt to access Myfiles app directly via app launcher or recents to see if authentication is bypassed
    Affected if Myfiles app opens without prompting for lock screen credentials - this confirms the bypass vulnerability is present

A device is affected if it runs Android 11.0 or 12.0 with S Secure installed at a version predating the SMR Apr-2022 Release 1, and has lock screen security enabled which can be bypassed to access Myfiles without credentials.

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 SMR Apr-2022 Release 1 security update to Samsung devices running S Secure. Organizations should ensure physical security controls are in place for devices until the update is deployed.

Recommended fix Moderate confidence

SMR Apr-2022 Release 1

  1. Identify your Samsung device model
  2. Navigate to Settings > About Phone > Software Information to check current Android version (11.0 or 12.0)
  3. Go to Settings > Software Update and tap 'Download and Install' to check for available updates
  4. If SMR Apr-2022 Release 1 is available, download and install the update
  5. After updating, verify the patch is applied by checking Settings > About Phone > Software Information > Security patch level

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

Fix this in Android 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 help mitigating

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-25832 — 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-25832 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