dbcve.org
AndroidOperating system · Google

CVE-2022-28783

HIGH · 7.1 CVSS v3.1 Published 2022-05-03
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
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 validation of removing package name in Galaxy Themes prior to SMR May-2022 Release 1 allows attackers to uninstall arbitrary packages without permission. The patch adds proper validation logic for removing package name.

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

In Samsung Galaxy Themes prior to the SMR May-2022 Release 1, the application lacked proper validation when processing package removal requests. This allowed any caller to trigger uninstallation of arbitrary packages without authentication or authorization checks. The vulnerability resided in the package name removal function where user-supplied input was not validated against permitted actions, enabling an attacker to craft requests that uninstalled any installed application.

MitigationApply the SMR May-2022 Release 1 patch which adds proper validation logic to verify package removal requests are legitimate before execution. Until the patch is applied, limit the application's exposure to untrusted input sources.

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
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 Samsung Galaxy Themes app is installed
    Run 'pm list packages | grep themes' or check for 'com.samsung.android.themecenter' in the package manager
    Affected if The package com.samsung.android.themecenter appears in the installed packages list
  2. Retrieve the installed Samsung Galaxy Themes version
    Execute 'dumpsys package com.samsung.android.themecenter | grep versionName' or use a package info viewer to get the versionName field
    Affected if A version string is returned, indicating the app is installed with a specific version number
  3. Compare version against the May-2022 patch release
    Identify whether the installed version is earlier than the SMR May-2022 Release 1 patch version - check release notes or firmware documentation for the exact fixed version number
    Affected if The installed version predates the SMR May-2022 Release 1 patch, meaning the missing validation for package removal requests is present
  4. Confirm Android OS version in use
    Check system settings or run 'getprop ro.build.version.release' to determine the Android version
    Affected if The device runs Android 10.0, 11.0, or 12.0 with an unpatched Samsung Galaxy Themes app

If Samsung Galaxy Themes is installed on Android 10, 11, or 12 and the app version is older than the SMR May-2022 Release 1 patch, the device is vulnerable to unauthenticated package removal.

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 May-2022 Release 1 patch which adds proper validation logic to verify package removal requests are legitimate before execution. Until the patch is applied, limit the application's exposure to untrusted input sources.

Recommended fix High confidence

Samsung Galaxy devices: May-2022 SMR (Security Patch Level) or later

  1. Check the current Android security patch level on the affected Samsung Galaxy device by going to Settings > About Phone > Software Information > Security patch level
  2. Navigate to Settings > Software Update and tap 'Download and install' to check for available updates
  3. Update to the May-2022 SMR (Security Maintenance Release) or later, which includes the patch for CVE-2022-28783
  4. Verify the security patch level has been updated to May-2022 or newer after the update completes

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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