CVE-2022-27822
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 · uneditedInformation exposure vulnerability in ril property setting prior to SMR April-2022 Release 1 allows access to EF_RUIMID value without 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 confidenceThis is an information disclosure vulnerability in Samsung's Radio Interface Layer (ril) property setting mechanism. The flaw allows untrusted applications to read the EF_RUIMID value from the SIM/RUIM card without requiring the READ_PHONE_STATE permission, bypassing Android's standard permission model for sensitive SIM identifier data.
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= 10.0= 11.0= 12.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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 10.0, 11.0, or 12.0 (the affected versions listed)
-
Identify if Samsung RIL is in useRun 'getprop ro.ril' via ADB or check for Samsung-specific RIL libraries in /system/lib/ or /vendor/lib/Affected if Samsung RIL implementation is present (this is a Samsung-specific vulnerability in their ril property setting mechanism)
-
Verify EF_RUIMID access without permission is possibleAttempt to read the EF_RUIMID value via the RIL interface without holding READ_PHONE_STATE permission - this requires examining the ril property setting behavior or using a test app that requests EF_RUIMIDAffected if Untrusted applications can read EF_RUIMID from SIM/RUIM card without READ_PHONE_STATE permission being granted
A user is affected if they are running Android 10.0, 11.0, or 12.0 on a Samsung device with their RIL implementation, where untrusted apps can access the EF_RUIMID SIM identifier without proper permission checks.
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 SMR April-2022 Release 1 security patch which adds proper permission enforcement for ril property settings to prevent unauthorized access to EF_RUIMID.
Samsung SMR (Security Maintenance Release) April-2022 or later
- Check your current Android version by going to Settings > About Phone > Android version
- Go to Settings > Software update > Download and install to check for available updates
- Ensure your device is connected to Wi-Fi and charged during the update process
- Download and install the SMR April-2022 Release 1 or later security update
- After installation, verify the patch level by going to Settings > About Phone > Software information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27822 — 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-27822 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