Application crash via out-of-bounds column writes
Published Jun 4, 2025 · Updated Mar 27, 2026
Buffer overflow in Wireshark 4.2.0 through 4.2.12 and 4.4.0 through 4.4.6 allows attackers to crash it via malformed packets. The column utility module's col_clear and col_set_str operations write beyond a 4,096-byte heap allocation while CLNP packet data is dissected. Exploitation requires an injected live packet or user interaction to open a crafted capture file, and the demonstrated consequence is process termination.
Summary
What happened
Buffer overflow in Wireshark 4.2.0 through 4.2.12 and 4.4.0 through 4.4.6 allows attackers to crash it via malformed packets. The column utility module's col_clear and col_set_str operations write beyond a 4,096-byte heap allocation while CLNP packet data is dissected. Exploitation requires an injected live packet or user interaction to open a crafted capture file, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2025-5601
- Published
- Jun 4, 2025
- Updated
- Mar 27, 2026
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, CWE-120, T1204.002, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2025CVE publishedPublication date reported by the CVE source.
- Mar 27, 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.0 <4.2.13
- Affected versionversion=4.4.0 <4.4.7
What conditions does exploitation require?
What is affected?
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
- Fuzz job crash capture 20509proof 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