mirrors/tcpdump
0
0
Fork 0
mirror of https://github.com/the-tcpdump-group/tcpdump.git synced 2024-11-24 10:33:28 +08:00
Code Issues Packages Projects Releases Wiki Activity
35a8fc576d
tcpdump/tests/pimv2-oobr-3.out

11 lines
573 B
Plaintext
Raw Normal View History

Use UTC/GMT time when building/checking tests files This will avoid some differences when checking in different time zones. We now run the tests without the '-t' option. This will allow to get problems/changes in time printing functions. Update the output of the tests accordingly. Moreover: Add the '-#' option to better identify a packet when there is a difference in output.
2018-08-04 14:46:17 +08:00
1 00:00:00.000000 c2:02:52:72:00:00 > 01:00:5e:00:00:0d, ethertype IPv4 (0x0800), length 65535: (tos 0xc0, ttl 1, id 927, offset 0, flags [none], proto PIM (103), length 65521)
CVE-2017-12996/PIMv2: Make sure PIM TLVs have the right length. We do bounds checks based on the TLV length, so if the TLV's length is too short, and we don't check for that, we could end up fetching data past the end of the TLV - including past the length of the captured data in the packet. This fixes a buffer over-read discovered by Forcepoint's security researchers Otto Airamo & Antti Levomäki. Add tests using the capture files supplied by the reporter(s).
2017-02-14 03:31:25 +08:00
10.0.0.2 > 224.0.0.13: PIMv2, length 65501
Hello, cksum 0xaa6e (incorrect)
Hold Time Option (1), length 2, Value: 1m45s
0x0000: 0069
Generation ID Option (20), length 4, Value: 0x3f0ef4cd
0x0000: 3f0e f4cd
DR Priority Option (19), length 4, Value: 1
0x0000: 0000 0001
PIM: Fix some length checks Update the outputs of some tests accordingly.
2019-11-09 21:04:04 +08:00
State Refresh Capability Option (21), length 2, Value: [option length 2 != 4] (invalid)
Reference in New Issue Copy Permalink