CVE-2020-9241
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 · uneditedHuawei 5G Mobile WiFi E6878-370 with versions of 10.0.3.1(H563SP1C00),10.0.3.1(H563SP21C233) have an improper authorization vulnerability. The device does not restrict certain data received from WAN port. Successful exploit could allow an attacker at WAN side to manage certain service of the device.
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 confidenceThe Huawei 5G Mobile WiFi E6878-370 contains an improper authorization vulnerability in firmware versions 10.0.3.1(H563SP1C00) and 10.0.3.1(H563SP21C233). The device fails to properly restrict certain data received from the WAN port, allowing an attacker on the WAN side to manage certain services on the device without proper authorization.
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.3.1\(h563sp1c00\)= 10.0.3.1\(h563sp21c233\)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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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 device modelAccess the device admin interface or check the device label to confirm the model is Huawei E6878-370Affected if Device is not the E6878-370 model
-
Check firmware versionNavigate to the device web admin interface, typically at 192.168.1.1 or 192.168.8.1, and locate the firmware version under Settings > Device Information or System > VersionAffected if Firmware version is 10.0.3.1(H563SP1C00) or 10.0.3.1(H563SP21C233)
-
Verify WAN exposureCheck the device's network configuration to determine if it is connected directly to an ISP-provided WAN/5G network without an intervening firewall, or if the management web interface is accessible from the WAN IPAffected if Device management interface is reachable from WAN side or device has direct WAN-facing exposure
-
Inspect WAN-facing servicesFrom a system on the WAN side, attempt to access the device admin portal using the public WAN IP or test if common management ports (80, 443, 8080) are listening on the WAN interfaceAffected if Management services respond to requests originating from WAN
Device is affected if it is a Huawei E6878-370 running firmware 10.0.3.1(H563SP1C00) or 10.0.3.1(H563SP21C233) AND has management interfaces accessible from the WAN side.
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 firmware update when available from Huawei. Until then, restrict WAN-facing exposure by placing the device behind a properly configured firewall and avoid exposing management interfaces to untrusted networks.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9241 — 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-2020-9241 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