CVE-2023-0612
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 · uneditedA vulnerability, which was classified as critical, was found in TRENDnet TEW-811DRU 1.0.10.0. Affected is an unknown function of the file /wireless/basic.asp of the component httpd. The manipulation leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-219936.
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 confidenceBuffer overflow vulnerability in TRENDnet TEW-811DRU router firmware 1.0.10.0 in the httpd web server's /wireless/basic.asp page allows remote attackers to potentially execute arbitrary code via crafted HTTP requests. Public exploit (VDB-219936) exists.
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= 1.0.10.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 access the router's web interface and look for the model number in the status or system information pageAffected if The device is not a TRENDnet TEW-811DRU router, then this CVE does not apply
-
Check the firmware versionAccess the router's web interface and navigate to the System or Administration section to view the firmware version, or use the command 'cat /proc/version' via telnet/ssh if availableAffected if The firmware version is exactly 1.0.10.0, indicating the vulnerable version
-
Verify the httpd web server is runningCheck if the router's web management interface is accessible by attempting to access the router's IP address on ports 80 or 443Affected if The httpd web server is running and responding to HTTP requests
-
Confirm the /wireless/basic.asp endpoint existsAttempt to access the URL path /wireless/basic.asp on the router's web interface (e.g., http://[router-ip]/wireless/basic.asp)Affected if The /wireless/basic.asp page is accessible and returns a valid HTTP response
-
Check network exposure of the management interfaceDetermine if the router's web interface is accessible from untrusted networks by reviewing firewall rules or attempting access from an external networkAffected if The management interface is exposed to untrusted networks, allowing remote attackers to reach the vulnerable endpoint
The environment is affected if you have a TRENDnet TEW-811DRU router running firmware version 1.0.10.0 with the httpd web server and /wireless/basic.asp page accessible, particularly if exposed to untrusted networks.
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 dataCheck TRENDnet for firmware updates; if unavailable, restrict management interface access to trusted networks or replace the device.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0612 — 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-0612 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