dbcve.org
AndroidOperating system · Google

CVE-2022-30727

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 handling of insufficient permissions vulnerability in addAppPackageNameToAllowList in PersonaManagerService prior to SMR Jun-2022 Release 1 allows local attackers to set some setting value in work space.

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 confidence

Improper permission handling in Samsung's PersonaManagerService allows local attackers to bypass authorization checks in the addAppPackageNameToAllowList function, enabling modification of workspace settings without proper privileges. This is a local authorization bypass affecting Samsung devices prior to the June 2022 security update.

MitigationApply Samsung SMR (Security Maintenance Release) June 2022 Release 1 or later to patch the PersonaManagerService vulnerability. No additional configuration changes are specified in the vulnerability disclosure.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Confirm device is a Samsung device
    Check the device manufacturer by running 'getprop ro.product.manufacturer' or checking Settings > About Phone > Manufacturer
    Affected if Manufacturer is not Samsung - the vulnerability is specific to Samsung's PersonaManagerService
  2. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Version is 10.0, 11.0, or 12.0 - these are the affected Android versions listed for this CVE
  3. Check security patch level
    Run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Security patch level
    Affected if The patch level is earlier than 2022-06-01 - the vulnerability was patched in the June 2022 Samsung SMR (Security Maintenance Release)
  4. Verify PersonaManagerService presence
    Check if the service exists by running 'dumpsys | grep -i persona' or 'service list' to enumerate available system services
    Affected if PersonaManagerService is present and accessible to local applications - the vulnerability allows local apps to bypass authorization in the addAppPackageNameToAllowList function

A Samsung device running Android 10, 11, or 12 with a security patch level earlier than June 2022 is likely affected by this authorization bypass in PersonaManagerService.

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 Samsung SMR (Security Maintenance Release) June 2022 Release 1 or later to patch the PersonaManagerService vulnerability. No additional configuration changes are specified in the vulnerability disclosure.

Recommended fix High confidence

SMR Jun-2022 Release 1 or later

  1. Check your Samsung device model and carrier for the availability of the SMR (Samsung Mobile Security) June 2022 Release 1 update
  2. Navigate to Settings > Software Update on your Samsung device
  3. Tap 'Download and install' to check for and apply the latest security patch
  4. Alternatively, manually flash the firmware containing SMR Jun-2022 Release 1 or later via Odin/firmware download

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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