Security Resilience

CVE-2024-9780

Wireshark 4.4.0

Public PoC
Published
10 October 2024
Modified
17 October 2024
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 56 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-9780 is a high-severity Missing Initialization of a Variable (CWE-456) vulnerability in Wireshark. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

ITS dissector crash in Wireshark 4.4.0 allows denial of service via packet injection or crafted capture file

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-3201Same product: Wireshark Wireshark
CVE-2024-8250Same product: Wireshark Wireshark
CVE-2023-5371Same product: Wireshark Wireshark
CVE-2025-5601Same product: Wireshark Wireshark
CVE-2026-5403Same product: Wireshark Wireshark
CVE-2023-0667Same product: Wireshark Wireshark
CVE-2026-5405Same product: Wireshark Wireshark
CVE-2026-6533Same product: Wireshark Wireshark
CVE-2026-6535Same product: Wireshark Wireshark
CVE-2026-6869Same product: Wireshark Wireshark

Affected Assets

wireshark
wireshark
4.4.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover uninitialized variables through static analysis or dynamic checks.

Documented development processes and coding standards can mandate initialization of all critical variables.

Secure engineering principles can require explicit variable initialization in design and coding standards.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require static analysis and coding standards that enforce variable initialization.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect uninitialized-variable conditions through static and dynamic analysis.

prevents

Secure coding standards directly require explicit initialization of all variables before use.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-909, a class-level weakness, and none of its children carries one either.

References