CVE-2020-14079
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 a stack-based buffer overflow in the ssi binary. The overflow allows an authenticated user to execute arbitrary code by POSTing to apply.cgi via the action auto_up_fw (or auto_up_lp) with a sufficiently long update_file_name key.
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 confidenceThe TRENDnet TEW-827DRU router through firmware version 2.06B04 contains a stack-based buffer overflow in the ssi binary. An authenticated attacker can achieve remote code execution by sending a POST request to apply.cgi with the action parameter set to 'auto_up_fw' or 'auto_up_lp' and providing an excessively long value for the update_file_name parameter, which overwrites stack memory and allows arbitrary code execution.
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 device modelLog into the router web interface or check the device label/marketing materials to confirm the exact model is TRENDnet TEW-827DRUAffected if The device is a TRENDnet TEW-827DRU router
-
Check the firmware versionAccess the router administration panel, typically at 192.168.1.1, and navigate to the Status or System section to view the firmware version. Alternatively, check the download page on TRENDnet's official support site for your device.Affected if The installed firmware version is 2.06B04 or any earlier version (versions are typically listed as like 2.06B04, 2.05B01, etc.)
-
Determine if remote management is accessibleCheck the router's web interface for remote management settings (often under Administration > Remote Management or similar). Verify if the management interface is accessible from WAN/internet by attempting to access the router's public IP on ports 80 or 443 from an external network.Affected if Remote management is enabled and the router's admin interface is reachable from untrusted networks
-
Check if default credentials are in useAttempt to log into the router with the default credentials (check TRENDnet documentation for default username/password, commonly admin/admin or admin/password). Also verify whether the password has been changed from defaults.Affected if The router still uses default administrative credentials or easily guessable credentials
Your environment is affected if you have a TRENDnet TEW-827DRU router running firmware version 2.06B04 or earlier, with remote management enabled or default credentials in use on an exposed interface.
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 dataSince this is an authenticated RCE in end-of-life hardware firmware, primary remediation requires either applying an available vendor firmware update if one exists, or implementing network segmentation to restrict access to the device's management interface. If no firmware update is available, the device should be replaced with a supported model.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14079 — 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-14079 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