dbcve.org
E5332 FirmwareOperating system · Huawei

CVE-2014-5328

MEDIUM · 6.8 CVSS v2.0 Published 2014-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Buffer overflow in the Webserver component on the Huawei E5332 router before 21.344.27.00.1080 allows remote authenticated users to cause a denial of service (reboot) via a long parameter in an API service request message.

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 confidence

Buffer overflow in the Webserver component of Huawei E5332 routers allows authenticated remote users to send API service requests with excessively long parameters, causing the device to crash and reboot. This is a stack-based buffer overflow in the webserver handling of API request messages.

MitigationUpdate Huawei E5332 firmware to version 21.344.27.00.1080 or later. If patching is not immediately possible, restrict administrative access to trusted IP addresses to reduce attack surface.

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
E5332 FirmwareOperating system
Affected:= 21.344.19.00.1080
E5332Hardware / appliance
Affected:all versions

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
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/C:N/I:N/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Huawei E5332 model and firmware version
    Access the router web interface (typically http://192.168.1.1) and navigate to Device Information or Status page to view the exact firmware version. Alternatively, check the device label or use telnet/SSH to access and run 'AT+CVERSION?' or similar diagnostic command.
    Affected if The device is a Huawei E5332 with firmware version 21.344.19.00.1080, or if the 'all versions' statement applies, any firmware version on this model.
  2. Verify webserver component is accessible
    Attempt to reach the router web interface by browsing to the device IP address on ports 80 or 443 from a remote location. Use curl or a browser to check if the HTTP service responds.
    Affected if The webserver responds to requests, indicating the API service component is active and reachable.
  3. Check remote authentication status
    Log into the router web interface and navigate to Settings > Security or Administration section. Look for options related to remote management, web access from WAN, or TR-069 remote configuration. Verify if remote authenticated access is enabled.
    Affected if Remote management or authenticated access from WAN is enabled, allowing external users to send API requests to the device.
  4. Identify network exposure
    Check router firewall settings and port forwarding rules. Determine if ports 80/443 or the API service port are exposed to the internet by performing an external port scan or reviewing the router security settings.
    Affected if The router webserver/API ports are exposed to untrusted networks or the internet, allowing remote attackers to reach the service.

A user is affected if they have a Huawei E5332 router with any firmware version where the webserver API service is accessible remotely and authenticated remote access is enabled, allowing external users to send specially crafted API requests with excessively long parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Huawei E5332 firmware to version 21.344.27.00.1080 or later. If patching is not immediately possible, restrict administrative access to trusted IP addresses to reduce attack surface.

Fix this in E5332 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-5328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-5328 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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