CVE-2022-38689
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 telephony service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.
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 · moderate confidenceA missing permission check in the Android telephony service allows local applications to access sensitive telephony information (such as call logs, voicemail, or SIM data) without proper authorization. Since no additional execution privileges are required, any installed app can potentially retrieve this information.
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 the Android OS 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 exactly (as specified in the affected versions)
-
Verify telephony service is accessibleConfirm the device has telephony capabilities (SIM card inserted, mobile network service active). Check via Settings > Network & Internet > SIM cards or run 'getprop gsm.sim.state' in ADB shellAffected if Telephony service is active and running on the device
-
Test for missing permission enforcement in telephony APIsAttempt to query call log content (android.provider.CallLog) or voicemail content (android.provider.VoicemailContract) from an app WITHOUT holding READ_CALL_LOG or READ_VOICEMAIL permissions. Use an app like a simple test app or ADB command: 'content query --uri content://call_log/calls'Affected if The query succeeds and returns call log, voicemail, or SIM data without the app having been granted the required runtime permissions
-
Confirm no system-level permission check blocks the accessReview logcat output (adb logcat) for any permission denial messages (e.g., 'Permission Denial') when accessing telephony content providers without permissionsAffected if No permission denial occurs and sensitive telephony data is returned to the caller without authorization checks
If the device runs Android 10.0, 11.0, or 12.0 and applications can read call logs, voicemail, or SIM data without holding READ_CALL_LOG, READ_VOICEMAIL, or similar permissions, the environment is affected by CVE-2022-38689.
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.
From vendor dataImplement and enforce proper permission checks in all telephony service APIs and code paths that handle sensitive data. Use Android's built-in permission enforcement mechanisms (e.g., checkCallPhone, READ_CALL_LOG) before returning any telephony information to callers.
- 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-38689 — 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-38689 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