CVE-2023-1992: Buffer over-read in Wireshark
Affects WiresharkSource CVE Database V5
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
- 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:LExploitation evidence
Disclosed: evidence found.
CVE published 12 Apr 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubwireshark/wiresharkpkg:github/wireshark/wiresharkOther threats | Affected
| Fixed in
|
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
- wireshark.org/security/wnpa-sec-2023-09.html (opens in a new tab)
- gitlab.com/wireshark/wireshark/-/issues/18852 (opens in a new tab)
- gitlab.com/gitlab-org/cves/-/blob/master/2023/CVE-2023-1992.json (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EHLTD25WNQSPQNELX52UH6YLP4TBLKTT/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PFJERBHVWYLYWXO2B3V47QH66IEB6EZ3/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FZA7IMATNNQPLIM6WMRPM3T5ZY24NRR2/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2023/04/msg00029.html (opens in a new tab)
- debian.org/security/2023/dsa-5429 (opens in a new tab)
- security.gentoo.org/glsa/202309-02 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/09/msg00049.html (opens in a new tab)