Process crash via unchecked BLF container lengths
Published May 26, 2023 · Updated Jan 15, 2025
Heap-buffer overflow in Wireshark 3.6.0 through 3.6.13 and 4.0.0 through 4.0.5 allows attackers to crash it via a crafted BLF file. The blf_pull_logcontainer_into_memory function copies 28 bytes into a 15-byte heap allocation after accepting inconsistent BLF container values. Exploitation requires a user to open the malformed capture file, corrupting heap state and terminating the Wireshark or TShark process.
Summary
What happened
Heap-buffer overflow in Wireshark 3.6.0 through 3.6.13 and 4.0.0 through 4.0.5 allows attackers to crash it via a crafted BLF file. The blf_pull_logcontainer_into_memory function copies 28 bytes into a 15-byte heap allocation after accepting inconsistent BLF container values. Exploitation requires a user to open the malformed capture file, corrupting heap state and terminating the Wireshark or TShark process.
The record
- CVE
- CVE-2023-2857
- Published
- May 26, 2023
- Updated
- Jan 15, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Jan 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=3.6.0, <3.6.14
- Affected versionversion=>=4.0.0, <4.0.6
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.
Public exploit references
- Upstream BLF crash reproducerproof 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