Disputed analyzer crash via buffer misaccounting
Published Feb 21, 2024 · Updated Nov 4, 2025
Claimed buffer overflow in Wireshark before 4.2.0 allows remote attackers to crash the analyzer through unspecified remote input. The reported flaw concerns format_fractional_part_nsecs in wsutil/to_str.c, where callers appended using the original buffer pointer and size instead of the current position and remaining space. Wireshark states that the report rests on invalid assumptions and that no released version was affected.
Summary
What happened
Claimed buffer overflow in Wireshark before 4.2.0 allows remote attackers to crash the analyzer through unspecified remote input. The reported flaw concerns format_fractional_part_nsecs in wsutil/to_str.c, where callers appended using the original buffer pointer and size instead of the current position and remaining space. Wireshark states that the report rests on invalid assumptions and that no released version was affected.
The record
- CVE
- CVE-2024-24479
- Published
- Feb 21, 2024
- Updated
- Nov 4, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=40
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
No public exploit references are available in this record.
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