CVE-2020-14075
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 · uneditedTRENDnet TEW-827DRU devices through 2.06B04 contain multiple command injections in apply.cgi via the action pppoe_connect, ru_pppoe_connect, or dhcp_connect with the key wan_ifname (or wan0_dns), allowing an authenticated user to run arbitrary commands on the device.
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 confidenceMultiple command injection vulnerabilities exist in TRENDnet TEW-827DRU routers (firmware up to 2.06B04). The apply.cgi script does not properly sanitize input to the wan_ifname and wan0_dns parameters when processing pppoe_connect, ru_pppoe_connect, or dhcp_connect actions, allowing authenticated attackers to execute arbitrary OS commands.
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<= 2.06b04CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelAccess the router web interface or check the device label/marketing to confirm the model is TEW-827DRUAffected if The device is a TRENDnet TEW-827DRU router
-
Check the installed firmware versionLog into the router web interface and navigate to Status or System section to view the firmware version. Alternatively, check via telnet/SSH if enabled, or inspect the kernel/bootlog if accessible.Affected if Firmware version is 2.06B04 or earlier
-
Verify if the web management interface is accessibleAttempt to reach the router's web interface from the network segment where the device is deployed. Check if port 80 or 443 is open on the device IP.Affected if The web interface is accessible from an untrusted network segment and authentication credentials are known or guessable
-
Determine if PPPoE or DHCP WAN connections are configuredIn the router web interface, check WAN settings under Internet Setup or similar section to see if PPPoE, Ru_PPPoE, or DHCP connection types are in useAffected if WAN connection type is set to PPPoE, Ru_PPPoE, or DHCP and the apply.cgi script handles these connections
You are affected if you have a TEW-827DRU router running firmware 2.06B04 or earlier, the router web interface is accessible to attackers, and the device uses PPPoE or DHCP WAN configuration.
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 dataUpdate router firmware to a patched version once available. Restrict web interface access to trusted users only until patched. If no patch exists, consider network segmentation or device replacement.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14075 — 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-2020-14075 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