Service interruption via malformed NFS packet
Published Jan 24, 2023 · Updated Nov 3, 2025
Memory leakage in Wireshark's NFS dissector in 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allows attackers to interrupt analysis. The NFS string-decoding path accepts malformed filename bytes as display strings, and repeated dissection leaves memory unreleased. A malformed packet must be injected onto a captured network, or a user must open a crafted capture file; sustained processing can consume excessive CPU resources.
Summary
What happened
Memory leakage in Wireshark's NFS dissector in 3.6.0 through 3.6.10 and 4.0.0 through 4.0.2 allows attackers to interrupt analysis. The NFS string-decoding path accepts malformed filename bytes as display strings, and repeated dissection leaves memory unreleased. A malformed packet must be injected onto a captured network, or a user must open a crafted capture file; sustained processing can consume excessive CPU resources.
The record
- CVE
- CVE-2023-0417
- Published
- Jan 24, 2023
- Updated
- Nov 3, 2025
- Vendor
- Wireshark Foundation
- Product
- Wireshark
- Classifications
- CWE-404, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 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.11
- Affected versionversion=>=4.0.0, <4.0.3
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
- Wireshark NFS fuzz capture 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