CPU exhaustion via regressing GDSDB parser offset
Published May 26, 2023 · Updated Nov 3, 2025
Denial of service in the GDSDB dissector of Wireshark 3.6.0 through 3.6.13 and 4.0.0 through 4.0.5 allows attackers to exhaust CPU. The add_uint_string() error path returns the remaining byte count as a new absolute offset, which can move parsing backward instead of consuming the buffer. A malformed injected packet or crafted capture file must reach the dissector, causing an infinite loop and sustained CPU consumption.
Summary
What happened
Denial of service in the GDSDB dissector of Wireshark 3.6.0 through 3.6.13 and 4.0.0 through 4.0.5 allows attackers to exhaust CPU. The add_uint_string() error path returns the remaining byte count as a new absolute offset, which can move parsing backward instead of consuming the buffer. A malformed injected packet or crafted capture file must reach the dissector, causing an infinite loop and sustained CPU consumption.
The record
- CVE
- CVE-2023-2879
- Published
- May 26, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-835, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.
Weakness, pattern, technique
Public exploit references
- fuzz-2023-05-13-7062.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