CVE-2023-44018
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 · uneditedTenda AC10U v1.0 US_AC10UV1.0RTL_V15.03.06.49_multi_TDE01 was discovered to contain a stack overflow via the domain parameter in the add_white_node 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 confidenceStack-based buffer overflow in Tenda AC10U v1.0 firmware (US_AC10UV1.0RTL_V15.03.06.49_multi_TDE01). The vulnerability exists in the add_white_node function where the domain parameter is not properly bounds-checked before being copied to a stack-allocated buffer, allowing potential remote code execution or denial of service.
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= 15.03.06.49_multi_tde01CVSS 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.
-
Confirm the firmware version of the Tenda AC10U deviceLog into the router admin panel and navigate to System Settings > Firmware Upgrade, or check the version label on the device itself. Alternatively, use the router's web interface status page or check via telnet/SSH if enabled.Affected if The firmware version is exactly 15.03.06.49_multi_tde01 (US_AC10UV1.0RTL_V15.03.06.49_multi_TDE01)
-
Verify the router's web management interface is accessible from the networkAttempt to access the router's IP address on ports 80 or 443 from a remote host. Check firewall rules or port forwarding configurations that may expose the admin interface externally.Affected if The web management interface is reachable from untrusted networks (not just the local LAN)
-
Identify if the add_white_node function is reachableThe add_white_node function is part of the whitelist/whitelisting feature. Check if the router has a Domain Whitelist or Access Control feature in the web interface under sections like Access Control, Firewall, or Parental Controls.Affected if The whitelist/whitelisting feature exists and is accessible in the router firmware
-
Inspect HTTP requests to the router's/cgi-bin/ directoryUse a web proxy or curl to examine if the router responds to requests at endpoints like /cgi-bin/ or specific API calls related to whitelist management. Look for parameters named 'domain' in POST requests.Affected if The router accepts HTTP POST requests with a 'domain' parameter to the CGI endpoint
-
Check for signs of exploitation or anomalous behaviorReview router logs for failed authentication attempts, unusual DNS proxy configurations, or unexpected processes. Monitor network traffic for suspicious outbound connections from the router.Affected if Logs show evidence of attempts to invoke the whitelist function or unexpected configurations
A user is affected if they are running Tenda AC10U firmware version 15.03.06.49_multi_tde01 AND the router's web interface is accessible (either locally or remotely) with the whitelist feature available.
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 patch when available. Until then, disable remote web management, restrict administrative interface access to trusted IPs only via firewall rules, and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44018 — 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-2023-44018 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