CVE-2020-14081
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 send_log_email with the key auth_acname (or auth_passwd), 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 confidenceTRENDnet TEW-827DRU routers through firmware 2.06B04 contain command injection vulnerabilities in the apply.cgi web interface. The send_log_email action fails to sanitize the auth_acname and auth_passwd parameters, allowing authenticated users to inject and execute arbitrary OS commands on the device.
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 device modelAccess the router web interface or check the device label/metadata to confirm the model is TRENDnet TEW-827DRUAffected if Device model is not TEW-827DRU, then not affected by this specific CVE
-
Check firmware versionLog into the router web interface and navigate to Status or System section to view the firmware version. Compare against the affected version 2.06B04 or lowerAffected if Firmware version is 2.06B04 or earlier, then the device is running a vulnerable version
-
Verify web interface accessibilityDetermine if the router web interface (apply.cgi) is reachable from the network. Check if the device is powered on and connected. Attempt to access the login page via HTTP/HTTPSAffected if Web interface is not accessible at all, then the attack surface does not exist though the vulnerability still exists in the firmware
-
Confirm authentication is configuredCheck router security settings to see if administrator credentials are set. The vulnerability requires valid authentication, so verify if any admin account existsAffected if No authentication is configured on the device, then the specific injection point via authenticated params auth_acname and auth_passwd would not be reachable as described in the CVE
Device is affected if it is a TRENDnet TEW-827DRU router running firmware version 2.06B04 or lower with its web interface accessible and administrative credentials configured.
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 to vendor-supplied patched firmware if available; if end-of-life, isolate the device behind a firewall, restrict administrative access to trusted IPs, and consider replacement. The vulnerability requires valid authentication, so enforcing strong credentials and monitoring for unauthorized access attempts is critical.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14081 — 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-14081 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