CVE-2022-21764
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 possible information disclosure due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07044717; Issue ID: ALPS07044717.
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 a telecom service allows local attackers to access sensitive information without requiring additional privileges or user interaction. The vulnerability exists in the permission validation logic of the affected telecom component.
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.
-
Identify Android versionCheck the device or system settings to determine the installed Android OS version, or use 'getprop ro.build.version.release' commandAffected if The version is 10.0, 11.0, or 12.0 (exact match)
-
Verify telecom service is presentCheck if the telecom service component is installed and running on the system. Look for telecom-related services in the system service list using 'dumpsys' or similar diagnostic toolsAffected if The telecom service is present and running on the device
-
Check telecom service permission configurationExamine the telecom service manifest or permission configuration files to determine what permission checks are currently enforced on sensitive data access pointsAffected if The telecom service is missing or has weak permission validation on sensitive data endpoints
-
Test local access to telecom dataFrom a local unprivileged application or shell context, attempt to query telecom service APIs or content providers to access sensitive information without holding elevated permissionsAffected if Sensitive telecom data is accessible without requiring appropriate permissions (no permission check is enforced)
-
Review telecom service entry pointsAnalyze all public interfaces, broadcasts, and content providers exposed by the telecom service for proper permission enforcementAffected if Any telecom service entry point returns sensitive data without verifying caller permissions
A user is affected if their Android device runs version 10.0, 11.0, or 12.0 and the telecom service allows unprivileged local access to sensitive data without permission validation.
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 dataApply patch ALPS07044717 to implement proper permission checks in the telecom service. Verify that all telecom service entry points enforce appropriate permission validation before returning any sensitive data.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21764 — 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-21764 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