CVE-2021-46834
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 · uneditedA permission bypass vulnerability in Huawei cross device task management could allow an attacker to access certain resource in the attacked devices. Affected product versions include:JAD-AL50 versions 102.0.0.225(C00E220R3P4).
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 permission bypass vulnerability in Huawei's cross-device task management feature on the JAD-AL50 device (firmware 102.0.0.225) allows an attacker to bypass authentication or authorization controls to access certain device resources. This is a medium-severity (CVSS 5.5) issue stemming from insufficient access control enforcement in the cross-device task management functionality.
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= 102.0.0.225\(c00e220r3p4\)CVSS 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.
-
Confirm device modelIdentify the Huawei device model number. This vulnerability specifically affects the JAD-AL50 model. Check device settings, about phone, or physical device labeling.Affected if Device model is not JAD-AL50 (different models have different vulnerability status)
-
Check firmware versionNavigate to device Settings > About Phone > Version information, or use *#*#2846579#*#* service code to access engineering menu, then check FW version. The affected firmware is 102.0.0.225(c00e220r3p4).Affected if Firmware version matches 102.0.0.225(c00e220r3p4) exactly
-
Verify cross-device task management featureLocate the cross-device task management feature in device settings. This may be under Settings > Huawei Share > Cross-device Task, Settings > Device Connections > Multi-screen Collaboration, or similar Huawei connectivity settings. Check if the feature toggle exists and is active.Affected if Cross-device task management feature is enabled on the device
-
Review feature permissionsCheck the permissions granted to the cross-device task management component. Navigate to Settings > Apps > Cross-device Task (or similar name) > Permissions. Verify if the feature has permissions that could be exploited for unauthorized resource access.Affected if Feature has excessive permissions granted (e.g., storage, contacts, or system settings access)
User is affected if they own a JAD-AL50 device running firmware 102.0.0.225(c00e220r3p4) with cross-device task management feature enabled.
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 the vendor-supplied firmware patch when released by Huawei; until then, disable or restrict cross-device task management features to limit the attack surface.
- 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-2021-46834 — 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-46834 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