CVE-2022-22291
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 · uneditedLogging of excessive data vulnerability in telephony prior to SMR Feb-2022 Release 1 allows privileged attackers to get Cell Location Information through log of user device.
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 the Android telephony subsystem. The telephony module is logging excessive data, specifically Cell Location Information (which reveals the user's geographic location based on cell tower data), to persistent logs. Privileged attackers with access to the device logs can read this sensitive location data, enabling physical tracking of the device owner.
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 ADB shellAffected if The version is 10.0, 11.0, or 12.0 (exact matches)
-
Examine telephony logs for cell location dataRun 'logcat -d | grep -i cell' or 'logcat -d | grep -i location' via ADB shell to view saved logcat outputAffected if Logs contain entries with Cell ID, LAC, or geographic coordinates from the telephony module
-
Review logcat radio bufferRun 'logcat -d -b radio' via ADB shell to examine the radio buffer where telephony messages are storedAffected if Radio buffer entries show Cell Location Information being logged with coordinates or cell tower identifiers
-
Check for persistent log filesExamine /data/log/ or /data/misc/logd/ directories via ADB shell for saved log files containing telephony dataAffected if Persistent log files exist and contain telephony location data entries
A device is affected if it runs Android 10.0, 11.0, or 12.0 AND its logs (logcat, radio buffer, or persistent log files) contain Cell Location Information that reveals geographic position.
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 · scopedUpdate the device to Samsung's SMR Feb-2022 Release 1 or later, which contains the patch removing Cell Location Information from telephony logs. Alternatively, if updates are unavailable, review and sanitize telephony logging code to ensure no location-revealing data is written to logs.
SMR Feb-2022 Release 1 or later
- Check current SMR (Samsung Mobile Security) version on the device via Settings > About Phone > Software Information > Security software version
- Upgrade the device to SMR (Security Maintenance Release) Feb-2022 Release 1 or later through Settings > Software Update > Download and Install
- Verify the device is running SMR Feb-2022 Release 1 or newer after update completes
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-22291 — 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-22291 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