Friday, March 29, 2024

Wireshark 3.0.7 Released – Fixes for Security Vulnerabilities & Update for BGP, IEEE 802.11, TLS Protocols

Wireshark 3.0.7 released with a number of security updates and fixed several other bugs that reside in the Wireshark components.

Wireshark also updated Protocol Support for various protocols such as BGP, HomePlug AV, IEEE 802.11, and TLS.

Wireshark is known as the world’s most popular network protocol analyzer. It is used for troubleshooting, analysis, development, and education.

It is used by network administrators to troubleshoot network and by the security, analyst to examine the packets. It is a widely used tool in organizations.

Wireshark 3.0.7 fixed the vulnerability {CVE-2019-19553)) that resides in the CMS dissector that affected the Wireshark version 3.0.0 to 3.0.6, 2.6.0 to 2.6.12.

“It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.”

Other Fixed Bugs in Wireshark 3.0.7

  • ws_pipe_wait_for_pipe() can wait on closed handles. Bug 15696.
  • Support for 11ax in PEEKREMOTE. Bug 15740.
  • The temporary file …​ could not be opened: Invalid argument. Bug 15751.
  • Reassembling of the two TLS records is not working correctly. Bug 16109.
  • Display Filter Area: Dropdown Missing pkt_comment and tcp.options.sack_perm (likely others). Bug 16130.
  • Display Filter autocompletion should be disabled. Bug 16132.
  • BGP Linkstate IP Reachability information is incorrect. Bug 16144.
  • NGAP: ExpectedUEActivityBehaviour decode error. Bug 16145.
  • HomePlug AV dissector: MMTYPE and FMI fields are dissected incorrectly. Bug 16158.
  • JPEG files cannot be saved on Windows with french language. Bug 16165.
  • X11 –display interpreted as –display-filter which maps to -Y option. Bug 16167.
  • “Create new file automatically after” not working with extcap. Bug 16178.
  • Encrypted TLS alerts sometimes listed as decrypted. Bug 16180.
  • The “Remove Wireshark from the system path” package has “Add Wireshark to the system PATH” as its title. Bug 16200.
  • tshark -T ek -x causes get_field_data: code should not be reached. Bug 16218.
  • Crash on Go → Next/Previous Packet in Conversation when no packet is selected. Bug 16228.

The new version of Wireshark can be downloaded from here.

Training Course: Master in Wireshark Network Analysis – Hands-on course provides a complete network analysis Training using Wireshark.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Website

Latest articles

Google Revealed Kernel Address Sanitizer To Harden Android Firmware And Beyond

Android devices are popular among hackers due to the platform’s extensive acceptance and open-source...

Compromised SaaS Supply Chain Apps: 97% of Organizations at Risk of Cyber Attacks

Businesses increasingly rely on Software as a Service (SaaS) applications to drive efficiency, innovation,...

IT and security Leaders Feel Ill-Equipped to Handle Emerging Threats: New Survey

A comprehensive survey conducted by Keeper Security, in partnership with TrendCandy Research, has shed...

How to Analyse .NET Malware? – Reverse Engineering Snake Keylogger

Utilizing sandbox analysis for behavioral, network, and process examination provides a foundation for reverse...

GoPlus’s Latest Report Highlights How Blockchain Communities Are Leveraging Critical API Security Data To Mitigate Web3 Threats

GoPlus Labs, the leading Web3 security infrastructure provider, has unveiled a groundbreaking report highlighting...

Wireshark 4.2.4 Released: What’s New!

Wireshark stands as the undisputed leader, offering unparalleled tools for troubleshooting, analysis, development, and...
Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Mitigating Vulnerability Types & 0-day Threats

Mitigating Vulnerability & 0-day Threats

Alert Fatigue that helps no one as security teams need to triage 100s of vulnerabilities.

  • The problem of vulnerability fatigue today
  • Difference between CVSS-specific vulnerability vs risk-based vulnerability
  • Evaluating vulnerabilities based on the business impact/risk
  • Automation to reduce alert fatigue and enhance security posture significantly

Related Articles