Application crash via unchecked OPUS frame count
Published Oct 27, 2022 · Updated May 9, 2025
Stack-based buffer overflow in Wireshark 3.6.0 through 3.6.8 allows attackers to crash the application via malformed OPUS packets. In dissect_opus(), frame_count can exceed MAX_FRAMES_COUNT before parse_size_field writes frame data beyond the fixed stack array. Processing injected traffic requires the dissector to receive the malformed packet; opening a crafted capture requires user interaction, and either path terminates Wireshark or TShark.
Summary
What happened
Stack-based buffer overflow in Wireshark 3.6.0 through 3.6.8 allows attackers to crash the application via malformed OPUS packets. In dissect_opus(), frame_count can exceed MAX_FRAMES_COUNT before parse_size_field writes frame data beyond the fixed stack array. Processing injected traffic requires the dissector to receive the malformed packet; opening a crafted capture requires user interaction, and either path terminates Wireshark or TShark.
The record
- CVE
- CVE-2022-3725
- Published
- Oct 27, 2022
- Updated
- May 9, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2022CVE publishedPublication date reported by the CVE source.
- May 9, 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.8
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
- rtp_opus_stackoverflow_poc.pcapproof 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