Wireshark (64-bit)

What's new in this version:

- 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
- 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” in order to reset the ChmodBPF Launch Daemon

Fixed:
- The following vulnerabilities have been fixed:
- wnpa-sec-2023-08 ISO 15765 and ISO 10681 dissector crash

The following bugs have been fixed:
- UTF-8 characters end up escaped in PSML output
- Export filtered displayed packets won’t save IP fragments of SCTP fragments needed to reassemble a displayed frame
- DICOM dissection in reassembled PDV goes wrong
- "Export Objects - IMF" produces incorrect file, TCP reassembly fails with retransmissions that have additional data
- The intelligent scroll bar or minimap is not predictable on locating and scrolling
- If you mark (or unmark) the currently-selected frame, the packet details still say it’s not marked (or it is marked) Issue 14330.
- An out-of-order packet incorrectly detected as retransmission breaks desegmentation of TCP stream
- Sorting Packet Loss Column is not sorting correct
- Some HTTPS packets cannot be decrypted
- SIP TCP decoding regression from Wireshark 1.99.0 to 3.6.8
- Frame comments not preserved when using filter to write new pcap from tshark
- ChmodBPF not working on macOS Ventura 13.1
- Wireshark GUI and window manager stuck after setting display filter
- Dissector bug, protocol H.261
- File extension heuristics are case-sensitive
- Symbolic links to packages in macOS dmg can’t be double-clicked to install on macOS 13.2
- Potential memory leak in tshark.c
- Fuzz job crash output: fuzz-2023-02-05-7303.pcap
- f5fileinfo: Hardware platforms missing descriptions
- The lines in the intelligent scrollbar are off by one
- Wireshark crashes on invalid UDS packet in Lua context
- TECMP dissector shows the wrong Voltage in Vendor Data
- UDS: Names of RDTCI subfunctions 0x0b …? 0x0e are not correct

Updated Protocol Support:
- ASTERIX, BGP, DHCP, ERF, F5 Ethernet trailer, GMR-1 RR, Gryphon, GSM SMS, H.261, H.450, ISO 10681, ISO 15765, MIPv6, NAS-5gs, NR RRC, NS Trace, OptoMMP, PDCP-LTE, PDCP-NR, QSIG, ROHC, RSVP, RTCP, SCTP, SIP, TCP, TECMP, TWAMP, UDS, and UMTS RLC