dbcve.org
Tew 823dru FirmwareOperating system · Trendnet

CVE-2014-8579

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-05
Fix available
A fix is available. Upgrade to after 1.00b30 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
TRENDnet TEW-823DRU devices with firmware before 1.00b36 have a hardcoded password of kcodeskcodes for the root account, which makes it easier for remote attackers to obtain access via an FTP session.

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 confidence

The TRENDnet TEW-823DRU router firmware versions prior to 1.00b36 contain a hardcoded credential (username: root, password: kcodeskcodes) that allows remote unauthenticated attackers to gain administrative access via FTP.

MitigationUpdate the device firmware to version 1.00b36 or later to remove the hardcoded credential. If updating is not possible, disable FTP access at the network perimeter and monitor for unauthorized access attempts.

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
Tew 823dru FirmwareOperating system
Affected:<= 1.00b30

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is TRENDnet TEW-823DRU
    Access the router web interface or check the device label/marketing materials to verify the exact model number
    Affected if The device is not a TRENDnet TEW-823DRU
  2. Check the installed firmware version
    Log into the router web interface and navigate to the Status or Firmware Upgrade page to view the current firmware version, or check via CLI if available
    Affected if The firmware version is 1.00b30 or earlier (any version <= 1.00b30)
  3. Verify FTP service is enabled on the router
    Access the router administration panel and look for FTP server settings under Network or Services settings, or attempt to connect to the router's IP on TCP port 21 from an internal network host
    Affected if FTP service is active and accessible on the network
  4. Test for the hardcoded credential
    Attempt an FTP login to the router using the credentials root/kcodeskcodes (username: root, password: kcodeskcodes)
    Affected if The hardcoded credentials successfully authenticate and grant administrative access

A user is affected if they own a TRENDnet TEW-823DRU router running firmware version 1.00b30 or earlier with FTP enabled and the hardcoded credentials still active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.00b30
Interim mitigation

Update the device firmware to version 1.00b36 or later to remove the hardcoded credential. If updating is not possible, disable FTP access at the network perimeter and monitor for unauthorized access attempts.

Recommended fix High confidence

TRENDnet TEW-823DRU Firmware 1.00b36 or later

  1. 1. Download the latest firmware version 1.00b36 or later from the official TRENDnet support website (trendnet.com)
  2. 2. Connect a computer to the TEW-823DRU router via Ethernet cable
  3. 3. Open a web browser and access the router's web interface at http://192.168.10.1
  4. 4. Log in to the router administration panel with current admin credentials
  5. 5. Navigate to the 'Administration' or 'Firmware Upgrade' section in the web interface
  6. 6. Click 'Browse' or 'Choose File' and select the downloaded firmware file
  7. 7. Click 'Upload' or 'Upgrade' to apply the new firmware
  8. 8. Wait for the upgrade process to complete (do not power off the device)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tew 823dru Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8579 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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