CVE-2023-25214
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 AC5 US_AC5V1.0RTL_V15.03.06.28 was discovered to contain a stack overflow via the setSchedWifi function. This vulnerability allows attackers to cause a Denial of Service (DoS) or execute arbitrary code via a crafted payload.
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 confidenceA stack buffer overflow vulnerability exists in the setSchedWifi function of Tenda AC5 router firmware US_AC5V1.0RTL_V15.03.06.28. The vulnerability allows remote attackers to cause a Denial of Service or achieve arbitrary code execution by sending a crafted payload to the affected function, likely through the web interface.
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.28CVSS 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 router modelCheck the device label or web interface for the exact model number (Tenda AC5)Affected if Device is not a Tenda AC5 router - different models are not affected by this specific CVE
-
Check the firmware versionAccess the router's web management interface and look for a Firmware Version or Software Version field in the System or Administration settings, or use 'grep' or 'cat' on /proc/version if you have shell accessAffected if Firmware version is exactly 15.03.06.28 (the only affected version listed)
-
Verify the setSchedWifi function existsIf you have shell access, search the firmware binary or web server binaries for the string 'setSchedWifi' using strings or grepAffected if The setSchedWifi function is present in the firmware
-
Confirm web interface is accessibleAttempt to access the router's web interface on the typical HTTP ports (80/443) from an internal network hostAffected if The web management interface is exposed and reachable (this is the attack vector)
-
Check for signs of exploitationReview router logs for unusual or malformed requests to the setSchedWifi function, or monitor network traffic for unexpected POST requests to the web interfaceAffected if Logs show suspicious requests containing long strings or unexpected characters sent to setSchedWifi
The environment is affected only if the device is a Tenda AC5 router running firmware version 15.03.06.28 with the web management interface accessible and the setSchedWifi function present.
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-provided firmware patches when available; until then, restrict network access to the router's web management interface to minimize attack surface.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25214 — 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-25214 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