Unauthenticated data exposure via hard-coded download key
Published Aug 9, 2025 · Updated Aug 12, 2025
Hard-coded key use in Lighttpd on TRENDnet TN-200 1.02b02 allows remote attackers to read protected data via forged download tokens. The Lighttpd secdownload.secret setting stores the shared literal neV3rUseMe, so token validation cannot establish per-device authorization. No authentication or user interaction is required, although producing a valid token is high-complexity; the documented consequence is confidentiality loss only.
Summary
What happened
Hard-coded key use in Lighttpd on TRENDnet TN-200 1.02b02 allows remote attackers to read protected data via forged download tokens. The Lighttpd secdownload.secret setting stores the shared literal neV3rUseMe, so token validation cannot establish per-device authorization. No authentication or user interaction is required, although producing a valid token is high-complexity; the documented consequence is confidentiality loss only.
The record
- CVE
- CVE-2025-8759
- Published
- Aug 9, 2025
- Updated
- Aug 12, 2025
- Vendor
- TRENDnet
- Product
- TN-200
- Classifications
- CWE-321, T1550
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.02b02
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo