CVE-2022-47338
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 denial of service without proper authorization. The vulnerability stems from an endpoint or function that doesn't validate caller permissions before executing privileged 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.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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Check Android versionVerify the installed Android OS version on the device via Settings > About Phone > Android version, or use command 'getprop ro.build.version.release'Affected if Version is exactly 10.0 or 11.0
-
Identify telecom service statusRun 'dumpsys telecom' to check if the TelecomManager service is running and accessible on the deviceAffected if Telecom service is active and responding to queries
-
Verify permission enforcement on telecom entry pointsReview the telecom service implementation to confirm whether permission checks (e.g., MODIFY_PHONE_STATE or carrier privilege validation) are performed before executing sensitive operationsAffected if Telecom service lacks or has broken permission validation logic at entry points
-
Check for unauthorized telecom operation logsExamine logcat or system logs for denied telecom operations or permission check failures (filter for 'telecom' and 'permission' or 'denied' keywords)Affected if Logs indicate telecom operations were executed without proper authorization checks
-
Assess local app access to telecom serviceDetermine if any non-privileged local applications can directly invoke TelecomManager APIs without encountering permission enforcementAffected if Unprivileged apps can trigger telecom operations without permission errors
The environment is affected if the device runs Android 10.0 or 11.0 and the telecom service fails to validate caller permissions before executing privileged operations.
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 at all telecom service entry points, ensuring callers have required permissions (e.g., MODIFY_PHONE_STATE or carrier privileges) before allowing sensitive operations.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47338 — 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-47338 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