CVE-2022-20216
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 · uneditedandroid exported is used to set third-party app access permissions, and the default value of intent-filter is true. com.sprd.firewall has set exported as true.Product: AndroidVersions: Android SoCAndroid ID: A-231911916
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 · high confidenceThe com.sprd.firewall component in Android SoC has the exported attribute set to true, which improperly allows third-party applications to access and potentially manipulate firewall settings. Since intent-filter defaults to true, this exposes the firewall management interface to any installed app, enabling privilege escalation and unauthorized security configuration changes.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if com.sprd.firewall component exists on the deviceRun 'pm list packages | grep sprd' or 'pm list packages -3' to list third-party packages. Alternatively, use 'aapt dump badging <apk>' on the system image to search for the component.Affected if The package containing com.sprd.firewall is present on the device
-
Inspect the exported attribute of the com.sprd.firewall componentUse 'aapt dump badging <apk_path>' and look for the 'exported' flag in the component declaration, or decompile the APK and examine AndroidManifest.xml for the component definition.Affected if The component has android:exported="true" or has no android:exported attribute set (defaults to true when intent-filter exists)
-
Verify if the component declares any permissionsExamine the AndroidManifest.xml or aapt output to see if android:permission is defined on the com.sprd.firewall component. Check if signature-level permissions are required.Affected if No android:permission is defined, allowing any installed app to access the component
-
Confirm the component is accessible to third-party appsUse 'dumpsys package <component_name>' or check via ADB with 'pm dump' to verify the component accepts intents from other applications.Affected if The component accepts intents from non-system apps without restriction
The device is affected if the com.sprd.firewall component is present and its android:exported attribute is either set to true or not explicitly set to false, allowing any installed app to manipulate firewall settings.
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 dataSet android:exported="false" in the AndroidManifest.xml for the com.sprd.firewall component unless external app access is explicitly required. If legitimate third-party access is needed, implement proper permission checks and consider using signature-level permissions.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20216 — 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-20216 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