Memory corruption via unauthenticated username parameter
Published Mar 26, 2025 · Updated Mar 27, 2025
Stack overflow in Telesquare TLR-2005KSH 1.1.4 allows remote attackers to corrupt memory through an unauthenticated admin.cgi request. The disclosed locus is the setUsernamePassword request handler in admin.cgi, but the CNA reference set provides no accessible patch or source diff identifying the exact unsafe copy operation. No credentials or user interaction are required; the public record does not specify whether exploitation causes a crash or code execution.
Summary
What happened
Stack overflow in Telesquare TLR-2005KSH 1.1.4 allows remote attackers to corrupt memory through an unauthenticated admin.cgi request. The disclosed locus is the setUsernamePassword request handler in admin.cgi, but the CNA reference set provides no accessible patch or source diff identifying the exact unsafe copy operation. No credentials or user interaction are required; the public record does not specify whether exploitation causes a crash or code execution.
The record
- CVE
- CVE-2025-26011
- Published
- Mar 26, 2025
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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