CVE-2021-46788
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 · uneditedThird-party pop-up window coverage vulnerability in the iConnect module.Successful exploitation of this vulnerability may cause system pop-up window may be covered to mislead users to perform incorrect operations.
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 confidenceThis is a UI redress/clickjacking vulnerability in the iConnect module where third-party pop-up windows can overlay and cover legitimate system pop-ups. Attackers exploit this to mislead users into performing incorrect operations by obscuring the actual action they're confirming.
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.0= 10.1.0= 10.1.1= 11.0.0= 12.0.0= 3.0.0= 3.1.0= 3.1.1= 4.0.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Check EMUI or Magic UI versionNavigate to Settings > About Phone > Version, or use ADB command 'adb shell getprop ro.build.version.emui' for EMUI devices or 'adb shell getprop ro.build.version.magic' for Magic UI devicesAffected if Version equals 10.0.0, 10.1.0, 10.1.1, 11.0.0, or 12.0.0 for EMUI, or 3.0.0, 3.1.0, 3.1.1, or 4.0.0 for Magic UI
-
Verify iConnect module presenceCheck system apps list in Settings > Apps > All Apps, or use 'adb shell pm list packages' to search for iConnect packageAffected if iConnect module is installed and enabled on the device
-
Inspect webview security headersIf iConnect provides web-based interfaces, use a network proxy to intercept responses and check for X-Frame-Options and Content-Security-Policy headersAffected if No X-Frame-Options header set to DENY or SAMEORIGIN, and no frame-ancestors directive in CSP header, allowing third-party content to embed the interface
-
Test for clickjacking vulnerabilityOpen the iConnect module and attempt to trigger a system confirmation dialog, then try to overlay it with a third-party pop-up from another app to see if coverage is possibleAffected if Third-party pop-up windows can visually overlay and cover system pop-ups from iConnect
A device is affected if it runs one of the listed EMUI or Magic UI versions AND has the iConnect module enabled, with no frame protection headers preventing clickjacking attacks.
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 frame-busting scripts, X-Frame-Options headers (DENY or SAMEORIGIN), and Content Security Policy (frame-ancestors) to prevent third-party content from overlaying system interfaces; redesign pop-up flows to use modal dialogs that cannot be covered.
- 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-2021-46788 — 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-2021-46788 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