dbcve.org
Tn 200 FirmwareOperating system · Trendnet

CVE-2025-8759

MEDIUM · 5.9 CVSS v3.1 Published 2025-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability was found in TRENDnet TN-200 1.02b02. It has been declared as problematic. This vulnerability affects unknown code of the component Lighttpd. The manipulation of the argument secdownload.secret with the input neV3rUseMe leads to use of hard-coded cryptographic key . The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Hard-coded cryptographic key (neV3rUseMe) found in Lighttpd secdownload.secret component of TRENDnet TN-200 firmware 1.02b02 allows attackers to generate valid time-limited download URLs without authentication, enabling unauthorized access to sensitive files.

MitigationNo user-facing workaround exists; the vendor must release firmware update with removable/configurable cryptographic keys. Consider network segmentation and disabling the secdownload feature until patch available.

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
Tn 200 FirmwareOperating system
Affected:= 1.02b02

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify device model and firmware version
    Access the TRENDnet TN-200 web interface or check /proc/version or /etc/issue on the device console to confirm the device model and firmware version. Look for version 1.02b02 specifically.
    Affected if Firmware version is exactly 1.02b02 (the only affected version listed)
  2. Locate secdownload configuration
    On the device filesystem, look for lighttpd configuration files typically in /etc/lighttpd/ or /etc/. Search for files containing 'secdownload' or 'secret'. Common config files: lighttpd.conf, secdownload.conf, or included config fragments.
    Affected if A secdownload configuration file exists on the device
  3. Inspect secdownload.secret value
    Open the secdownload config file and locate the 'secdownload.secret' or 'secdownload.secretkey' parameter. Examine the value assigned to it.
    Affected if The secret value is hardcoded to 'neV3rUseMe' (the vulnerable key)
  4. Verify secdownload feature is enabled
    Check if secdownload is actually enabled in the lighttpd configuration. Look for 'secdownload.enable' set to '1' or 'true', and ensure the feature is not commented out.
    Affected if secdownload is enabled and configured to use the hardcoded key

You are affected if running TRENDnet TN-200 firmware 1.02b02 with secdownload feature enabled and the hardcoded key 'neV3rUseMe' present in the configuration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

No user-facing workaround exists; the vendor must release firmware update with removable/configurable cryptographic keys. Consider network segmentation and disabling the secdownload feature until patch available.

Recommended fix Moderate confidence
  1. Identify the affected TRENDnet TN-200 device running firmware version 1.02b02
  2. Review network exposure of the Lighttpd web interface - restrict access to trusted networks or VPN if possible
  3. If the secdownload.secret parameter is configurable, change it from the hardcoded value 'neV3rUseMe' to a unique, cryptographically strong secret
  4. Monitor TRENDnet's official support pages and firmware release notes for any future security updates
  5. Consider replacing the device if no official firmware patch becomes available, as the hardcoded key cannot be securely mitigated through configuration alone
Caveat No official fix available - vendor did not respond to disclosure. Upgrade path unknown.

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

Fix this in Tn 200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8759 — 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-2025-8759 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