Monday, April 7, 2025
HomeCyber Security NewsWireshark 4.0.5 Released With New Protocol Support

Wireshark 4.0.5 Released With New Protocol Support

Published on

SIEM as a Service

Follow Us on Google News

With improved protocol support, various bug fixes, and several enhancements, Wireshark has released version 4.0.5. On March 3, 2023, the most recent version of Wireshark 4.0.4 was made available; this is the second upgrade of this year.

The open-source packet analyzer Wireshark is free to use. It is employed in developing software and communications protocols, network troubleshooting, analysis, and education.

Wireshark is one of the most extensively used tools for analyzing network protocols and serves a variety of tasks.

- Advertisement - Google News

According to the Wireshark team, official 32-bit Windows packages are unavailable for Wireshark 4.0 and later.

“We do not ship official 32-bit Windows packages for Wireshark 4.0 and later. If you need to use Wireshark on that platform, we recommend using the latest 3.6 release”, Wireshark.

“If you’re running Wireshark on macOS and upgraded to macOS 13 from an earlier version, you will likely have to open and run the “Uninstall ChmodBPF” package, then open and run “Install ChmodBPF” to reset the ChmodBPF Launch Daemon.”

There are different operating systems for which the Wireshark packet analyzer is accessible, including Windows, Linux, macOS, and BSD.

Wireshark 4.0.5 Protocol Support

DHCP, DIS, DNS, ERF, FF, genl, GQUIC, GSM A-bis OML, HL7, IEEE 802.11, ITS, LAPD, netfilter, netlink-route, netlink-sock_diag, nl80211, RLC, RPCoRDMA, RTPS, SCTP, SMB, UDS, VNC, and WCP.

Bug Fixes

  • Wireshark ITS Dissector RTCMEM wrong protocol version selector 2 – should use 1. Issue 18862.
  • Wireshark treats the letter E in SSRC as an exponential representation of a number. Issue 18879.
  • VNC RRE Parser skips over data. Issue 18883.
  • sshdump coredump when –remote-interface is left empty. Issue 18904.
  • Fuzz job crash output: fuzz-2023-03-17-7298.pcap. Issue 18917.
  • Fuzz job crash output: fuzz-2023-03-27-7564.pcap. Issue 18934.
  • RFC8925 support (dhcp option 108) Issue 18943.
  • DIS dissector shows an incorrect state in the packet list info column. Issue 18967.
  • RTP analysis shows incorrect timestamp error when timestamp is rolled over. Issue 18973.
  • Asterisk (*) key crash on Endpoint/Conversation dialog. Issue 18975.
  • The RTP player waveform now synchronizes better with audio.

Vulnerabilities Fixes:

Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform.

A list of third-party packages can be found on the download page on the Wireshark website. Wireshark source code and installation packages are available.

Download:

You can Download the latest version of the application from the link here.

Struggling to Apply The Security Patch in Your System? – 

Related Coverage:

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Threat Actors Exploit Toll Payment Services in Widespread Hacking Campaign

In a sophisticated cybercrime operation, the Smishing Triad, a China-based group, has been identified...

Everest Ransomware Gang’s Leak Site Hacked and Defaced

TechCrunch has uncovered a concerning development in consumer-grade spyware: a stealthy Android monitoring app...

ToddyCat Attackers Exploited ESET Command Line Scanner Vulnerability to Conceal Their Tool

In a sophisticated cyberattack, the notorious ToddyCat APT group utilized a previously unknown vulnerability...

Threat Actors Use VPS Hosting Providers to Deliver Malware and Evade Detection

Cybercriminals are intensifying phishing campaigns to spread the Grandoreiro banking trojan, targeting users primarily...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Threat Actors Exploit Toll Payment Services in Widespread Hacking Campaign

In a sophisticated cybercrime operation, the Smishing Triad, a China-based group, has been identified...

Everest Ransomware Gang’s Leak Site Hacked and Defaced

TechCrunch has uncovered a concerning development in consumer-grade spyware: a stealthy Android monitoring app...

ToddyCat Attackers Exploited ESET Command Line Scanner Vulnerability to Conceal Their Tool

In a sophisticated cyberattack, the notorious ToddyCat APT group utilized a previously unknown vulnerability...