CVE-2021-22410
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 XSS injection vulnerability in iMaster NCE-Fabric V100R019C10. A module of the client does not verify the input sufficiently. Attackers can exploit this vulnerability by modifying input after logging onto the client. This may compromise the normal service of the client.
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 confidenceCross-site scripting (XSS) injection vulnerability in Huawei iMaster NCE-Fabric V100R019C10 client interface. An authenticated attacker can exploit insufficient input validation in a client-side module to inject malicious scripts, potentially compromising session integrity or executing arbitrary client-side code.
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= v100r019c10CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Huawei iMaster NCE-Fabric installationLocate the Huawei iMaster NCE-Fabric management interface in your environment - typically accessed via web browser on the management IP/hostname of the Fabric controllerAffected if The product Huawei iMaster NCE-Fabric is present in your environment
-
Confirm installed version is v100R019C10Access the product management interface and navigate to the About or System Information page to view the firmware version, or use the command line interface to query the version (e.g., display version or similar command)Affected if The installed version is exactly v100R019C10
-
Verify client interface module is accessibleLog into the iMaster NCE-Fabric web interface and navigate to the client-facing modules - the vulnerability exists in the client interface componentAffected if The client interface module is enabled and accessible to authenticated users
-
Check for unauthenticated network exposureDetermine if the iMaster NCE-Fabric management interface is directly accessible from untrusted networks (internet-facing or from less-trusted network segments)Affected if The management interface is reachable from network segments where untrusted users could obtain valid authentication credentials
Your environment is affected if you have Huawei iMaster NCE-Fabric version v100R019C10 deployed with the client interface module accessible to authenticated users.
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 robust input validation and output encoding for all user-supplied data in the affected module. Apply context-appropriate sanitization (HTML entity encoding, JavaScript escaping) and set Content-Security-Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22410 — 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-22410 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