576-byte memory leak via vpncmd exit
Published Mar 12, 2025 · Updated Jul 19, 2025
Memory leak in SoftEtherVPN 5.02.5187 allows attackers to leave 576 bytes allocated by exiting the vpncmd VPN Tools menu. The reported vpncmd exit path calls UnixMemoryAlloc for a 576-byte buffer but does not release that allocation after the quit action. Command-line access is required, and SoftEther disputes denial-of-service impact because the path performs only one small allocation.
Summary
What happened
Memory leak in SoftEtherVPN 5.02.5187 allows attackers to leave 576 bytes allocated by exiting the vpncmd VPN Tools menu. The reported vpncmd exit path calls UnixMemoryAlloc for a 576-byte buffer but does not release that allocation after the quit action. Command-line access is required, and SoftEther disputes denial-of-service impact because the path performs only one small allocation.
The record
- CVE
- CVE-2025-25566
- Published
- Mar 12, 2025
- Updated
- Jul 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 12, 2025CVE publishedPublication date reported by the CVE source.
- Jul 19, 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
- vpncmd 136-byte input validation procedureproof 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