CVE-2022-20268
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 · uneditedIn RestrictionsManager, there is a possible way to send a broadcast that should be restricted to system apps due to a permissions bypass. This could lead to local escalation of privilege on an enterprise managed device with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-210468836
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 confidenceIn RestrictionsManager on Android-13, a permissions bypass allows non-system applications to send broadcasts that should be restricted to system apps only. This enables local privilege escalation on enterprise managed devices without user interaction.
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= 13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if Version is exactly 13.0 (not 13.0.1 or higher)
-
Check if device is enterprise-managedLook for MDM/EMM enrollment via Settings > Security & privacy > Device admin, or check for MDM agent apps installed (e.g., Microsoft Intune, Samsung Knox, Google Endpoint Management)Affected if Device is enrolled in an enterprise mobility management (MDM/EMM) system
-
Check RestrictionsManager usageReview installed apps for use of android.app.admin.RestrictionsManager API, or check MDM policy configurations that leverage device restrictionsAffected if Enterprise-managed apps or MDM policies rely on RestrictionsManager to enforce restricted broadcasts
-
Verify system patch levelGo to Settings > About phone > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'Affected if Security patch level is earlier than the fix for CVE-2022-20268 (requires Android 13 security update)
Device is affected if running Android 13.0 (exact), is enterprise-managed, and has not received the Android-13 security patch that addresses this RestrictionsManager bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Android-13 security patch (available via Google/OEM updates) to all affected enterprise-managed devices. Use MDM/MCM policies to enforce system updates and verify patch compliance.
Android 13.0 with January 2023 Security Patch Level
- Check the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
- Apply the January 2023 Android Security Update or later through system update (Settings > System > Software Update)
- Verify the device has Security Patch Level: January 2023 or later after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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