CVE-2023-30373
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 · uneditedIn Tenda AC15 V15.03.05.19, the function "xian_pppoe_user" contains a stack-based buffer overflow 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 confidenceA stack-based buffer overflow vulnerability exists in the xian_pppoe_user function of Tenda AC15 firmware V15.03.05.19. This flaw allows an attacker to overflow a stack-allocated buffer, potentially enabling arbitrary code execution or denial of service by overwriting return addresses or adjacent stack variables.
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.05.19CVSS 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 modelLog into the Tenda router web interface (typically at 192.168.0.1) and check the device model information, or use commands like 'cat /proc/cpuinfo' via telnet/SSH if availableAffected if The device is not a Tenda AC15 router - if different model, this CVE does not apply
-
Check the firmware versionIn the router web interface, go to System Settings > Firmware Upgrade or System Status, and verify the exact firmware version string. Alternatively, check via telnet/SSH with 'cat /proc/version' or 'nvram get firmver'Affected if Firmware version is NOT exactly 15.03.05.19 - only this specific version is affected
-
Verify PPPoE configuration accessIn the router web interface, navigate to Advanced Settings > WAN Settings or Internet Settings. Look for PPPoE options (typically labeled 'PPPoE', 'ADSL', or 'Dynamic PPPoE'). Check if this configuration page is accessible and functional.Affected if PPPoE configuration is not available on this device - the vulnerable function xian_pppoe_user handles PPPoE user input and would not be exercised
-
Confirm xian_pppoe_user function presenceIf you have firmware binary access, extract and analyze the binary (typically '/bin/httpd' or similar). Use strings or binwalk to locate the 'xian_pppoe_user' function string. In the live device, check via telnet/SSH for any references in the web server binaries.Affected if The xian_pppoe_user function is not present in the running firmware - the vulnerability does not exist without this specific function code
You are affected if you are running Tenda AC15 firmware exactly version 15.03.05.19 and the PPPoE user configuration feature is accessible on your device.
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-supplied firmware patch when available; in interim, disable remote WAN management and enforce network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation8.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 $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30373 — 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-30373 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