Service interruption via excessive PNRP dissection loop
Published Nov 19, 2021 · Updated Aug 4, 2024
Excessive iteration in Wireshark 3.2.0 through 3.2.17 and 3.4.0 through 3.4.9 allows remote attackers to interrupt service. The PNRP dissector repeatedly adds the pnrp.segment.authority.flags.Lbit field to the protocol tree, exceeding one million items. A malformed packet reaching an active capture needs no authentication or user interaction; opening a crafted trace provides a second path to sustained CPU consumption.
Summary
What happened
Excessive iteration in Wireshark 3.2.0 through 3.2.17 and 3.4.0 through 3.4.9 allows remote attackers to interrupt service. The PNRP dissector repeatedly adds the pnrp.segment.authority.flags.Lbit field to the protocol tree, exceeding one million items. A malformed packet reaching an active capture needs no authentication or user interaction; opening a crafted trace provides a second path to sustained CPU consumption.
The record
- CVE
- CVE-2021-39923
- Published
- Nov 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-834, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.2.0, <3.2.18
- Affected versionversion=>=3.4.0, <3.4.10
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
- fuzz-2021-10-23-10060.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