dbcve.org
E5756s FirmwareOperating system · Huawei

CVE-2015-4629

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Huawei E5756S before V200R002B146D23SP00C00 allows remote attackers to read device configuration information, enable PIN/PUK authentication, and perform other unspecified actions.

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

The Huawei E5756S mobile WiFi hotspot contains a pre-authentication vulnerability allowing remote attackers to read sensitive device configuration and enable PIN/PUK authentication. The flaw exists in firmware versions prior to V200R002B146D23SP00C00, likely involving improper access controls on management interfaces accessible over the network.

MitigationUpgrade Huawei E5756S firmware to version V200R002B146D23SP00C00 or later. If immediate patching is not possible, restrict network access to the device's management interface by placing it behind a NAT or firewall.

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
E5756s FirmwareOperating system
Affected:<= v100r001b100d00sp00c00

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Identify device model
    Access the device web管理界面 or check the device label/sticker for the model number E5756S
    Affected if Device is not a Huawei E5756S mobile WiFi hotspot
  2. Check firmware version
    Log into the device admin panel and navigate to Device Information or Status page to view the firmware version; alternatively, check via AT commands or the device's web interface source code
    Affected if Firmware version is v100r001b100d00sp00c00 or any version prior to it (versions earlier than V200R002B146D23SP00C00)
  3. Verify management interface accessibility
    Attempt to access the device management web interface from an external network segment (http://192.168.1.1 or the device's LAN IP) without any login credentials
    Affected if The management interface responds and exposes configuration pages without requiring authentication
  4. Check for sensitive configuration exposure
    Access common management endpoints on the device (such as /config or status pages) via HTTP GET requests without authentication to see if sensitive data is returned
    Affected if Sensitive device configuration, PIN, PUK settings, or administrative parameters are visible without authentication

You are affected if you have a Huawei E5756S device running firmware version v100r001b100d00sp00c00 or earlier, and its management interface is network-accessible (which is the default state for this device).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Huawei E5756S firmware to version V200R002B146D23SP00C00 or later. If immediate patching is not possible, restrict network access to the device's management interface by placing it behind a NAT or firewall.

Recommended fix Moderate confidence

V200R002B146D23SP00C00 or later

  1. 1. Identify the current firmware version of the Huawei E5756S device by accessing the device management interface or checking system information.
  2. 2. Navigate to the official Huawei support website (www1.huawei.com) or authorized download portal.
  3. 3. Locate the firmware download section for the E5756S mobile WiFi device.
  4. 4. Download the fixed firmware version V200R002B146D23SP00C00 or later.
  5. 5. Access the device administration panel through the web interface (typically at 192.168.1.1 or similar).
  6. 6. Navigate to the firmware upgrade or system settings section.
  7. 7. Upload the downloaded firmware file and initiate the upgrade process.
  8. 8. Wait for the device to complete the firmware update and reboot automatically.
Caveat Review Huawei release notes for this specific model before upgrading; some firmware updates may reset configuration or change default settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in E5756s Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4629 — 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-2015-4629 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