Wireshark up to 4.1.x wsutil/to_str.c format_fractional_part_nsecs buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Wireshark up to 4.1.x. It has been classified as critical. Affected by this vulnerability is the function format_fractional_part_nsecs of the file wsutil/to_str.c. The manipulation leads to buffer overflow.
This vulnerability is documented as CVE-2024-24479. The attack can be initiated remotely. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in Wireshark up to 4.1.x (Packet Analyzer Software). This issue affects the function format_fractional_part_nsecs of the file wsutil/to_str.c. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is availability. The summary by CVE is:
Buffer Overflow vulnerability in Wireshark team Wireshark before v.4.2.0 allows a remote attacker to cause a denial of service via the wsutil/to_str.c, and format_fractional_part_nsecs components.
The weakness was released 02/21/2024 as c3720cff158c265dec2a0c6104b1d65954ae6bfd. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-24479 since 01/25/2024. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 215035 (Amazon Linux 2023 : wireshark-cli, wireshark-devel (ALAS2023-2025-837)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.2.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (215035). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://www.wireshark.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 215035
Nessus Name: Amazon Linux 2023 : wireshark-cli, wireshark-devel (ALAS2023-2025-837)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Wireshark 4.2.0
Patch: github.com
Timeline
01/25/2024 🔍02/21/2024 🔍
02/21/2024 🔍
02/06/2025 🔍
Sources
Product: wireshark.orgAdvisory: c3720cff158c265dec2a0c6104b1d65954ae6bfd
Status: Confirmed
CVE: CVE-2024-24479 (🔍)
GCVE (CVE): GCVE-0-2024-24479
GCVE (VulDB): GCVE-100-254441
Entry
Created: 02/21/2024 20:10Updated: 02/06/2025 04:25
Changes: 02/21/2024 20:10 (42), 03/13/2024 10:26 (1), 08/02/2024 16:50 (15), 08/30/2024 06:00 (12), 02/06/2025 04:25 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.