CVE-2019-5268
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 home routers have an input validation vulnerability. Due to input parameter is not correctly verified, an attacker can exploit this vulnerability by sending special constructed packets to obtain files in the device and upload files to some directories.
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 is an input validation vulnerability in Huawei home routers where improper verification of input parameters allows attackers to send specially crafted packets to read arbitrary files from the device filesystem and upload files to specific directories. This appears to be a path traversal or file inclusion issue.
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.2.2, < 10.0.2.7>= 10.0.2.3, < 10.0.2.5>= 9.0.3.3, < 10.0.2.5>= 9.0.2.23, < 10.0.2.5>= 9.0.2.3, < 10.0.2.5>= 9.0.3.9, < 10.0.2.6>= 9.0.3.9, < 10.0.2.5>= 10.0.2.8, < 10.0.2.9CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 router modelCheck the device label or web interface for the exact model number (Cd10, Cd16, Cd17, Cd18, Hirouter Cd15, Cd20, Cd21, or Cd30)Affected if Router model is not one of these eight listed models
-
Check firmware versionAccess router web admin panel, look in Settings > System > Firmware Version, or check via CLI if available. Compare against: Cd10: 10.0.2.2 to <10.0.2.7; Cd16: 10.0.2.3 to <10.0.2.5; Cd17: 9.0.3.3 to <10.0.2.5; Cd18: 9.0.2.23 to <10.0.2.5; Cd15: 9.0.2.3 to <10.0.2.5; Cd20: 9.0.3.9 to <10.0.2.6; Cd21: 9.0.3.9 to <10.0.2.5; Cd30: 10.0.2.8 to <10.0.2.9Affected if Firmware version falls within any of these vulnerable ranges
-
Verify remote management is enabledIn router web interface, go to Advanced Settings > Remote Management (or similar). Check if remote web access from WAN/Internet is permittedAffected if Remote management interface is enabled and accessible from WAN
-
Check network exposure of admin interfaceAttempt to access router web interface from external network (or check port forwarding/firewall rules). Look for port 80/443 or custom ports open to InternetAffected if Router administrative interface is reachable from WAN IP address
Router is affected if it is one of the eight listed models with firmware version within the vulnerable ranges AND remote management is accessible from the network.
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 data10.0.2.510.0.2.610.0.2.7
Apply vendor-supplied firmware updates from Huawei; if patches are unavailable, disable remote management interfaces and restrict network access to the router's administrative functions.
- Consultation3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5268 — 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-2019-5268 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