CVE-2024-45414
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 · uneditedThe HTTPD binary in multiple ZTE routers has a stack-based buffer overflow vulnerability in webPrivateDecrypt function. This function is responsible for decrypting RSA encrypted ciphertext, the encrypted data is supplied base64 encoded. The decoded ciphertext is stored on the stack without checking its length. An unauthenticated attacker can get RCE as root by exploiting this vulnerability.
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 · high confidenceStack-based buffer overflow in the webPrivateDecrypt function of the HTTPD binary in multiple ZTE routers. The function decodes base64-encoded RSA encrypted ciphertext and stores the decoded result on the stack without validating length, allowing stack memory corruption and root RCE by unauthenticated attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router admin interface or check the device label to confirm it is a ZTE router modelAffected if Device is not a ZTE router product
-
Check firmware versionLog into the router admin panel and navigate to Status or System Information to view the installed firmware version. Compare this version number to any official ZTE security advisories for CVE-2024-45414Affected if Firmware version is listed as affected in ZTE security advisories for this CVE
-
Verify HTTPD service availabilityConfirm the HTTPD binary is present on the device by accessing the router via SSH or checking the web service endpoints that expose the webPrivateDecrypt functionAffected if HTTPD service is running and the webPrivateDecrypt function endpoint is accessible
-
Check web management interface exposureDetermine if the router web management interface (port 80/443) is exposed to untrusted networks by reviewing port forwarding rules, WAN accessibility, or remote management settings in the router configurationAffected if Web management interface is accessible from WAN or untrusted networks
-
Confirm remote management is enabledIn the router admin panel, check if remote management or TR-069 features are enabled under Advanced or Administration settingsAffected if Remote management access is enabled, allowing unauthenticated attackers to reach the vulnerable function
A user is affected if they operate a ZTE router with a firmware version matching the affected range for CVE-2024-45414 and the router web management interface is exposed to untrusted networks where an unauthenticated attacker can send base64-encoded RSA ciphertext to the webPrivateDecrypt function.
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 vendor firmware patches from ZTE when available. As an interim measure, restrict or disable remote access to the router's web interface to limit attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45414 — 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-2024-45414 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