dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-45415

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-16
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
The HTTPD binary in multiple ZTE routers has a stack-based buffer overflow vulnerability in check_data_integrity function. This function is responsible for validating the checksum of data in post request. The checksum is sent encrypted in the request, the function decrypts it and stores the checksum on the stack without validating it. 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 confidence

Stack-based buffer overflow in the check_data_integrity function of the HTTPD binary in multiple ZTE routers. The function decrypts an encrypted checksum from POST request data and stores it on the stack without validating the decrypted value, allowing an unauthenticated attacker to overflow the buffer and achieve root RCE.

MitigationApply vendor firmware updates when available. If no update exists, disable remote administration interfaces or restrict HTTP access to trusted sources at the network perimeter to reduce attack surface.

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 checks

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

  1. Identify the device as a ZTE router
    Check the device model number, manufacturer label, or login page banner for 'ZTE' branding. Use commands like 'show version', 'cat /proc/cpuinfo', or check the web interface footer for model information.
    Affected if The device is a ZTE router model that runs the HTTPD binary for web management.
  2. Locate and determine the HTTPD binary version
    Access the router via SSH or telnet (if enabled) and locate the HTTPD binary, typically at paths like /usr/sbin/httpd, /bin/httpd, or /usr/bin/httpd. Run 'httpd -v', 'httpd -h', or use 'strings' on the binary to find version information.
    Affected if The HTTPD binary version cannot be verified or is older than any vendor-supplied patch version.
  3. Verify network exposure of the web management interface
    Check if the router's HTTP/HTTPS ports (80/443) are bound to WAN-facing interfaces or are accessible from untrusted networks. Use 'netstat -tulpn | grep httpd' or 'iptables -L -n' to inspect listening interfaces.
    Affected if Port 80 or 443 is listening on a WAN or otherwise publicly accessible interface.
  4. Confirm the vulnerable check_data_integrity function exists
    If you can extract the HTTPD binary (via firmware download or router shell), use binwalk, strings, or a disassembler to search for the function name 'check_data_integrity' or related strings like 'decrypt checksum' or 'integrity'.
    Affected if The binary contains the check_data_integrity function and it performs decryption without bounds checking on the decrypted checksum.
  5. Check firmware version against vendor advisories
    In the router's web interface (typically under Status, System, or Maintenance), note the firmware version. Compare this against ZTE's security advisories or release notes for CVE-2024-45415.
    Affected if The installed firmware version predates the vendor's patch date for this vulnerability.

If the device is a ZTE router with an exposed HTTPD web interface and the firmware or HTTPD binary version has not been updated to include the vendor patch, the environment is affected by this vulnerability.

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

Apply vendor firmware updates when available. If no update exists, disable remote administration interfaces or restrict HTTP access to trusted sources at the network perimeter to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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