Client crash via oversized logging filename
Published Mar 22, 2026 · Updated Mar 22, 2026
Denial of service in LabF Axessh 4.2 allows local users to crash the client through an oversized logging filename. The logging dialog accepts at least 500 characters in the Log file name field without rejecting its length, then processes the value when a Telnet connection starts. The user must enable session logging, paste the oversized value locally, and start the connection; the demonstrated consequence is an application crash.
Summary
What happened
Denial of service in LabF Axessh 4.2 allows local users to crash the client through an oversized logging filename. The logging dialog accepts at least 500 characters in the Log file name field without rejecting its length, then processes the value when a Telnet connection starts. The user must enable session logging, paste the oversized value locally, and start the connection; the demonstrated consequence is an application crash.
The record
- CVE
- CVE-2019-25590
- Published
- Mar 22, 2026
- Updated
- Mar 22, 2026
- Vendor
- LabF
- Product
- Axessh
- Classifications
- CWE-1282, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 2026CVE publishedPublication date reported by the CVE source.
- Mar 22, 2026Record 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=4.2
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
- Axessh 4.2 Log file name Denial of Service PoCproof of concept · demonstrated
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