dbcve.org
AndroidOperating system · Google

CVE-2022-24931

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
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 access control vulnerability in dynamic receiver in ApkInstaller prior to SMR MAR-2022 Release allows unauthorized attackers to execute arbitrary activity without a proper permission

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 an improper access control vulnerability in ApkInstaller's dynamic broadcast receiver. The receiver does not properly enforce permission checks, allowing any application to send intents that trigger arbitrary activity execution without authentication. This enables unauthorized apps to potentially install or manipulate APKs on the device.

MitigationUpdate ApkInstaller to the SMR MAR-2022 Release or later, which contains proper permission enforcement on the dynamic receiver. If update is not possible, implement explicit permission requirements and intent filter restrictions on the vulnerable receiver.

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

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 the Android version
    Check the device settings or run 'getprop ro.build.version.release' to confirm the Android version
    Affected if The version is Android 10.0 or Android 11.0 exactly
  2. Locate the ApkInstaller application
    Search the installed applications list for an app named ApkInstaller or any APK installer/manager application that may contain the vulnerable component
    Affected if ApkInstaller or a similar APK management app is installed on the device
  3. Examine the dynamic broadcast receiver configuration
    Decompile the ApkInstaller APK and inspect the AndroidManifest.xml file for the dynamic broadcast receiver definition, specifically checking for the 'android:exported' and permission attributes
    Affected if The receiver is exported without requiring any permission (missing 'android:permission' attribute or using a weak/custom permission that is not enforced)
  4. Verify permission enforcement on the receiver
    Review the receiver's intent-filter and permission declarations in the manifest to determine if any authentication or permission check is enforced before allowing intent handling
    Affected if No explicit android:permission attribute is defined on the receiver, or the defined permission can be obtained by any application without proper validation

A user is affected if running Android 10.0 or 11.0 with ApkInstaller installed, and the dynamic broadcast receiver is exported without proper permission enforcement in the manifest.

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

Update ApkInstaller to the SMR MAR-2022 Release or later, which contains proper permission enforcement on the dynamic receiver. If update is not possible, implement explicit permission requirements and intent filter restrictions on the vulnerable receiver.

Recommended fix High confidence

SMR MAR-2022 Release (Samsung Mobile Security March 2022 Patch)

  1. Check the current Android version on the Samsung device (Settings > About Phone > Android version)
  2. Navigate to Settings > Software Update and tap 'Download and install' to check for available updates
  3. Apply the Samsung SMR MAR-2022 Release security patch update when available
  4. Verify the patch was successfully applied by checking Settings > About Phone > Software information > Security patch level (should show March 2022 or later)

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