TLS certificate parser with filter crash

Summary

The Idea was to use a filter e.g. "x509if.id == 2.5.4.3". But since that appears to to be invalid I started back spacing till I got "x509if.id == 2" that appeared to be valid. That however crashes wireshark.

Steps to reproduce

To the filter field enter "x509if.id == 2"

What is the current bug behavior?

It causes wireshark to crash

What is the expected correct behavior?

Wireshark does not crash

Sample capture file

Looks like any where there are TLS 1.2 certificates

Relevant logs and/or screenshots

(Paste any relevant logs here)

3.6.6 (v3.6.6-0-g7d96674e)

Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.31, build 31107), with Qt 5.15.2, with libpcap, with GLib 2.66.4, with zlib 1.2.11, with Lua 5.2.4, with GnuTLS 3.6.3 and PKCS #11 (closed) support, with Gcrypt 1.8.3, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.44.0, with brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.10, with libsmi 0.4.8, with QtMultimedia, with automatic updates using WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler), with Minizip.

Running on 64-bit Windows 7, build 7600, with Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz (with SSE4.2), with 16160 MB of physical memory, with GLib 2.66.4, with Qt 5.15.2, with Npcap version 1.60, based on libpcap version 1.10.2-PRE-GIT, with c-ares 1.17.0, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with nghttp2 1.44.0, with brotli 1.0.9, with LZ4 1.9.3, with Zstandard 1.4.0, without AirPcap, with light display mode, without HiDPI, with LC_TYPE=English_United Kingdom.utf8, binary plugins supported (21 loaded).