CVE-2018-25426 Details
Description
WinMTR 0.91 contains a denial of service vulnerability that allows attackers to crash the application by sending a malformed payload file containing a large buffer of repeated characters. Attackers can create a specially crafted input file with 238 bytes of data to trigger a buffer overflow condition that causes the application to crash.
A denial-of-service vulnerability has been identified in WinMTR version 0.91. This issue allows attackers to crash the application by sending a malformed payload file that contains a large buffer of repeated characters. The vulnerability is triggered when the application processes an input file with 238 bytes of data, leading to a buffer overflow condition that causes the application to crash.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 1, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.exploit-db.com/exploits/45769 | [email protected] | ExploitThird Party AdvisoryVDB Entry |
| https://www.vulncheck.com/advisories/winmtr-denial-of-service-via-buffer-overflow | [email protected] | Third Party Advisory |
| http://winmtr.net | [email protected] | Product |
| http://winmtr.net/winmtr_download/ | [email protected] | Exploit |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| winmtr winmtr | 0.91 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 3, 2026 | Initial Analysis | [email protected] |
| May 30, 2026 | New CVE Received | [email protected] |