CVE-2022-20217
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 · uneditedThere is a unauthorized broadcast in the SprdContactsProvider. A third-party app could use this issue to delete Fdn contact.Product: AndroidVersions: Android SoCAndroid ID: A-232441378
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 confidenceThe SprdContactsProvider in Android contains an unprotected broadcast receiver that allows any third-party application to send a broadcast capable of deleting Fixed Dialing Number (FDN) contacts stored on the SIM. The vulnerability stems from a missing permission check on the broadcast intent handler, enabling unauthorized manipulation of protected contact data.
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 dataall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 if device uses Spreadtrum SoCCheck the device's system-on-chip (SoC) information via Settings > About Phone > Baseband or use 'getprop ro.hardware' in adb shellAffected if The device runs on a Spreadtrum (also known as Unisoc) chipset, as the vulnerable component is part of the SprdContactsProvider from this manufacturer
-
Verify SprdContactsProvider is presentCheck for the presence of the vulnerable APK: look for 'SprdContactsProvider.apk' or 'com.sprd.contacts.provider' in /system/app/ or /data/app/ directories via adb shellAffected if The SprdContactsProvider application is installed on the device, indicating the vulnerable broadcast receiver exists
-
Confirm FDN feature is enabledCheck if Fixed Dialing Numbers (FDN) is enabled on the device: go to Settings > Connections > SIM card manager > FDN, or check via 'content query --uri content://telecom/phone_accounts' in adb shellAffected if FDN is active and the SIM contains FDN contacts, making the deletion attack relevant and impactful
A user is affected if their Android device uses a Spreadtrum/Unisoc SoC with the SprdContactsProvider present and FDN contacts are enabled on the SIM card.
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 vendor-specific security patches from the SoC manufacturer (Spreadtrum) via system OTA updates. Device users should verify their Android version is patched through their device manufacturer's security bulletin.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20217 — 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-20217 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