CVE-2022-27837
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 · uneditedA vulnerability using PendingIntent in Accessibility prior to version 12.5.3.2 in Android R(11.0) and 13.0.1.1 in Android S(12.0) allows attacker to access the file with system privilege.
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 confidenceA vulnerability in the Accessibility service prior to version 12.5.3.2 (Android R) and 13.0.1.1 (Android S) allows improper use of PendingIntent that can be exploited to access files with system-level privileges. The issue stems from insufficient validation or protection of the PendingIntent, enabling a local attacker to manipulate the intent and perform unauthorized file operations.
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< 12.5.3.2< 13.0.1.1CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Identify Android versionGo to Settings > About Phone > Android version. Note whether the device runs Android R (11) or Android S (12+) as the version threshold differs.Affected if The Android version determines which version threshold applies: R uses 12.5.3.2, S uses 13.0.1.1
-
Check Samsung Accessibility versionGo to Settings > Apps > Accessibility (or Samsung Accessibility service) and view the version information typically shown in the app details.Affected if The installed version is below 12.5.3.2 on Android R, or below 13.0.1.1 on Android S
-
Confirm Accessibility service is enabledGo to Settings > Accessibility and check whether the Samsung Accessibility service is turned on or granted permissions.Affected if The service is active and the version is below the applicable threshold for your Android version
A user is affected if they are running Samsung Accessibility versions below 12.5.3.2 on Android R or below 13.0.1.1 on Android S, with the Accessibility service enabled.
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 · scoped12.5.3.213.0.1.1
Update the affected application to version 12.5.3.2 or higher for Android R, and version 13.0.1.1 or higher for Android S. Review PendingIntent usage in Accessibility service code to ensure proper intent flagging and validation.
Samsung Accessibility version 12.5.3.2 or higher (Android R/11.0); version 13.0.1.1 or higher (Android S/12.0)
- Open Settings on the Samsung device
- Navigate to Apps → Accessibility (or search for 'Accessibility' in Settings)
- Tap on Accessibility in the app list
- Check the current version displayed in the app info
- If version is below 12.5.3.2 (for Android 11/R) or below 13.0.1.1 (for Android 12/S), open Galaxy Store
- Search for 'Samsung Accessibility' and tap Update if an update is available
- Alternatively, check for system updates via Settings → Software Update → Download and install
- After updating, verify the Accessibility app version matches or exceeds the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2022-27837 — 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-27837 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