CVE-2021-22293
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 · uneditedSome Huawei products have an inconsistent interpretation of HTTP requests vulnerability. Attackers can exploit this vulnerability to cause information leak. Affected product versions include: CampusInsight versions V100R019C10; ManageOne versions 6.5.1.1, 6.5.1.SPC100, 6.5.1.SPC200, 6.5.1RC1, 6.5.1RC2, 8.0.RC2. Affected product versions include: Taurus-AL00A versions 10.0.0.1(C00E1R1P1).
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 vulnerability involves inconsistent interpretation of HTTP requests in affected Huawei products, where the server parses HTTP requests in a way that differs from expected behavior, potentially allowing attackers to craft requests that bypass security controls or access sensitive information through information leak.
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= v100r019c10= 6.5.1.1= 8.0.0= 10.0.0.1\(c00e1r1p1\)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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Huawei CampusInsight installation and versionCheck the installed version of CampusInsight by querying the product's about page, system information panel, or running 'version' command in the management interface. Look for version string v100r019c10.Affected if CampusInsight version is exactly v100r019c10
-
Identify Huawei ManageOne installation and versionsCheck the ManageOne deployment version through the management console, about page, or version query command. Look for versions 6.5.1.1 or 8.0.0.Affected if ManageOne version is exactly 6.5.1.1 or exactly 8.0.0
-
Identify Huawei Taurus AL00A firmware versionCheck the device firmware version through phone settings, about phone section, or by querying the baseband/modem version. Look for version 10.0.0.1(c00e1r1p1).Affected if Taurus AL00a firmware version is exactly 10.0.0.1(c00e1r1p1)
-
Verify HTTP parsing interfaces are exposedCheck if the product's HTTP API gateway, REST interface, or web management portal is accessible from network locations where untrusted HTTP requests could be received. Inspect firewall rules and reverse proxy configurations.Affected if HTTP management or API interfaces are reachable from external or untrusted networks
The environment is affected only if one of the specific product versions (CampusInsight v100r019c10, ManageOne 6.5.1.1 or 8.0.0, Taurus-AL00A 10.0.0.1(c00e1r1p1)) is installed AND its HTTP interfaces are network-accessible.
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 available vendor patches for CampusInsight, ManageOne, and Taurus-AL00A to the specified versions. If patches are unavailable, implement additional HTTP request validation at perimeter firewalls or WAF to normalize and sanitize incoming HTTP requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22293 — 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-22293 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