Skip to main content
CVE-2023-1992VulnerabilityPublished Updated

CVE-2023-1992: Buffer over-read 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, 06:26 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
4.6% chance of exploitation in 30 days – higher than 91% 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 2026-10-26.

What to do

Upgrade wireshark/wireshark to 4.0.5 or 3.6.13.

Affected software

ProductAffectedFixed in
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threatsAffected
  • <3.6.13
  • <4.0.5
Fixed in
  • 3.6.13
  • 4.0.5

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

AI-suggested

To mitigate CVE-2023-1992, European organizations should: 1) Immediately upgrade Wireshark to versions 3.6.13, 4.0.5, or later where the vulnerability is patched. 2) Implement strict policies to avoid opening capture files from untrusted or unknown sources. 3) Use sandboxing or containerization techniques to isolate Wireshark processes, limiting the impact of potential crashes. 4) Educate users and analysts about the risks of handling unverified capture files and encourage verification of file provenance. 5) Employ network segmentation and monitoring to detect and block malicious RPCoRDMA traffic that could trigger the vulnerability. 6) Integrate automated patch management to ensure timely updates of Wireshark and related tools. 7) Consider alternative analysis tools or offline analysis environments for suspicious capture files. 8) Maintain robust incident response plans to quickly recover from potential denial of service events affecting network analysis capabilities.

Description

RPCoRDMA 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…