CVE-2025-15682: Unauthenticated Resource Exhaustion
TBEA TLogger V2.1.0.0B0.0.0.0 contains an unauthenticated resource exhaustion vulnerability in its web server. An unauthenticated remote attacker can send PUT requests to the /tmp/ endpoint, causing the web server to create persistent files containing attacker-controlled data under /opt/myapp/webserver/. The generated files are not removed because the web server attempts to move them into a non-existent directory. Repeated requests can therefore exhaust available storage and cause a denial-of-service condition.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
TBEA TLoggerto a version that resolves this vulnerability.Fixed in V2.1.0.0B0.0.0.0 - Compensating control
Mitigate the PUT-to-/tmp unauthenticated access by restricting/blocking inbound HTTP requests so the web server endpoint /tmp does not accept PUT from unauthenticated users.
- Operational
After applying the remediation, check for and remove any persistent attacker-created files under /opt/myapp/webserver/ created by repeated PUT requests to /tmp, and verify the destination directory exists to prevent the web server from failing to move generated files.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-15682?
CVE-2025-15682 has a risk score of 36, indicating a moderate level of severity.
How do I fix CVE-2025-15682?
To mitigate CVE-2025-15682, restrict access to the /tmp/ endpoint and implement rate limiting on the web server.
Who is affected by CVE-2025-15682?
CVE-2025-15682 affects users of TBEA TLogger version 2.1.0.0B0.0.0.0.
What type of vulnerability is CVE-2025-15682?
CVE-2025-15682 is an unauthenticated resource exhaustion vulnerability.
Can an attacker exploit CVE-2025-15682 without authentication?
Yes, an unauthenticated remote attacker can exploit CVE-2025-15682 by sending PUT requests to the vulnerable endpoint.