Ac18 FirmwareOperating system · Tenda

CVE-2024-57575

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-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
Tenda AC18 V15.03.05.19 was discovered to contain a stack overflow via the ssid parameter in the form_fast_setting_wifi_set function.

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 overflow vulnerability in Tenda AC18 router firmware V15.03.05.19. The form_fast_setting_wifi_set function fails to properly validate the length of the ssid parameter before copying it to a stack buffer, allowing remote attackers to overflow the stack and potentially execute arbitrary code.

MitigationUpdate to patched firmware if available; otherwise, disable remote administration or restrict access to the router's web interface to trusted IPs only.

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
Ac18 FirmwareOperating system
Affected:= 15.03.05.19

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 model
    Check the router label or web interface to confirm the model is Tenda AC18
    Affected if Device is not a Tenda AC18 router
  2. Check firmware version
    Access the router web interface (typically at 192.168.0.1) and look under System Settings > Firmware Upgrade or Administration > Firmware version. Alternatively, check the firmware file header if you have a firmware dump.
    Affected if Firmware version is 15.03.05.19 exactly
  3. Verify the vulnerable web function exists
    Access the router web interface and look for the Fast WiFi Settings or Quick WiFi Settings page (form_fast_setting_wifi_set function). This is typically found under Wireless or WiFi settings.
    Affected if The Fast WiFi Settings function is present and accessible
  4. Check remote web management accessibility
    Determine if the router web interface is accessible from the WAN/internet by attempting to access the router's public IP on port 80/443, or check the router's Remote Management setting under System Settings > Remote Management.
    Affected if Remote web management is enabled and the router is accessible from the internet

You are affected only if you have a Tenda AC18 router running exactly firmware version 15.03.05.19 with the web interface accessible (especially remotely), as the buffer overflow occurs in the ssid parameter of the form_fast_setting_wifi_set WiFi settings function.

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 to patched firmware if available; otherwise, disable remote administration or restrict access to the router's web interface to trusted IPs only.

Fix this in Ac18 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57575 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