Skip to main content
VulnerabilityPublished Updated

CVE-2023-1994: Null Pointer Dereference in Wireshark

Affects WiresharkSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.0.5 or 3.6.13 when convenient.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.5, 3.6.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Apr 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade the Debian debian/wireshark package to 4.0.5 or 3.6.13.

Affected software

ProductAffectedFixed in
Debiandebian/wiresharkpkg:deb/debian/wiresharkOther threatsAffected
  • <4.0.5
  • <3.6.13
Fixed in
  • 4.0.5
  • 3.6.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade Wireshark to versions 3.6.13 or later, or 4.0.5 or later, where this vulnerability is fixed.
  2. Avoid opening capture files from untrusted or unknown sources to reduce risk of triggering the crash.
  3. Implement strict network segmentation and filtering to limit exposure to potentially malicious GQUIC traffic, especially on monitoring networks.
  4. Use sandboxing or isolated environments for analyzing untrusted capture files to prevent disruption of critical systems.
  5. Educate security teams about the risks of crafted capture files and encourage verification of file provenance before analysis.
  6. Monitor Wireshark usage logs and crash reports to detect potential exploitation attempts.
  7. Consider alternative or complementary network analysis tools during patching windows to maintain operational continuity.
  8. Collaborate with vendors and community to obtain timely patches and updates.
  9. Employ network intrusion detection systems to flag suspicious GQUIC traffic patterns that could indicate exploitation attempts.

Description

GQUIC dissector crash in Wireshark 4.0.0 to 4.0.4 and 3.6.0 to 3.6.12 allows denial of service via packet injection or crafted capture file

References

Community reviews

Loading reviews…