CVE-2021-22396
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 privilege escalation vulnerability in some Huawei products. Due to improper privilege management, a local attacker with common privilege may access some specific files in the affected products. Successful exploit will cause privilege escalation.Affected product versions include:eCNS280_TD V100R005C00,V100R005C10;eSE620X vESS V100R001C10SPC200,V100R001C20SPC200.
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 confidenceLocal privilege escalation vulnerability in Huawei eCNS280_TD and eSE620X vESS products due to improper privilege management. An authenticated attacker with common user privileges can access specific files they should not have access to, potentially allowing them to elevate to higher privileges.
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= v100r005c00= v100r005c10= v100r001c10spc200= v100r001c20spc200CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify Huawei eCNS280_TD or eSE620X vESS product in useLocate the device or system running Huawei eCNS280_TD or eSE620X vESS firmware by reviewing hardware inventory, network documentation, or device management interfacesAffected if The system is a Huawei eCNS280_TD or eSE620X vESS device
-
Check installed firmware versionAccess the device management interface or use the appropriate command (such as 'display version' or checking system information) to retrieve the current firmware versionAffected if The installed firmware version is v100r005c00 or v100r005c10 for eCNS280_TD, or v100r001c10spc200 or v100r001c20spc200 for eSE620X vESS
-
Verify common user access to sensitive filesUsing a common user account (non-admin), attempt to access system configuration files, password files, or privilege escalation-related system files that should be restricted to administrative usersAffected if A non-administrative user account can read or access files that should require elevated privileges
-
Check for unauthorized privilege indicatorsReview system logs and audit records for any instances where common user accounts accessed administrative files or executed privileged commands outside their normal scopeAffected if Logs show common user accounts accessing restricted files or performing privileged operations
A user is affected if they are running Huawei eCNS280_TD firmware v100r005c00/v100r005c10 or eSE620X vESS firmware v100r001c10spc200/v100r001c20spc200 and common user accounts can access files that should require elevated privileges.
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-provided patches for affected versions. Until patched, restrict local system access to trusted personnel only and monitor for unauthorized access attempts to sensitive system files.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22396 — 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-22396 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