CVE-2022-47464
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 telecom service, there is a missing permission check. This could lead to local denial of service in telecom service.
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 telecom service allows a local attacker to cause a denial of service. The vulnerability stems from an undocumented or improperly enforced permission boundary in the telecom subsystem, likely on Android, where a component fails to validate caller permissions before executing sensitive 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= 10.0= 11.0= 12.0= 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 versionCheck the device or system settings for the Android OS version. On most devices: Settings > About Phone > Android version. Or via command line: 'getprop ro.build.version.release' or 'adb shell getprop ro.build.version.release'Affected if The device runs Android 10.0, 11.0, 12.0, or 13.0
-
Confirm telecom service presenceVerify the telecom service (com.android.server.telecom) is installed and running on the device. Use: 'adb shell dumpsys telecom' or check via Settings > Apps > Show system apps, look for 'Telecom' or 'Phone' servicesAffected if The telecom service is present and active on the device
-
Check for exposed telecom interfacesExamine if any third-party apps have been granted telecom permissions (like ANSWER_PHONE_CALLS, READ_PHONE_STATE, or PROCESS_OUTGOING_CALLS) that could interact with the telecom subsystem. Review via: 'adb shell dumpsys package <package_name>' for installed appsAffected if Apps with telecom-related permissions are installed and can interact with the telecom service
-
Verify service accessibilityCheck if the telecom service binds to any exposed binder interfaces or intents that could be reached by local apps. Use: 'adb shell service list' to list all running services and identify telecom-related entriesAffected if The telecom service exposes binder interfaces accessible to other local applications on the device
A device is affected if it runs Android 10.0, 11.0, 12.0, or 13.0 and has the telecom service enabled, making the missing permission check exploitable by local applications.
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 proper permission checks in the telecom service code path, ensuring all sensitive operations validate the caller's permissions before execution. Apply the principle of least privilege to restrict access to telecom functions.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47464 — 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-47464 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