Project

General

Profile

Actions

Bug #4463

closed

Wireshark dissector: integer overflow in NDNLP 'Sequence' field

Added by Junxiao Shi over 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
Due date:
% Done:

100%

Estimated time:

Description

Environment: Wireshark 2.4.3 on Windows 10

Input packet:

0000   64 fd 05 c6 51 08 00 00 00 00 00 53 54 0b 52 02  d...Q......ST.R.
0010   00 00 53 02 00 02 50 fd 05 b0 05 fd 07 fe 07 fd  ..S...P.........
0020   07 ea 08 01 55 08 01 50 08 fd 07 d0 58 58 58 58  ....U..P....XXXX
0030   58 58 58 58 58 58 58 58 58 58 58 58 58 58 58 58  XXXXXXXXXXXXXXXX
(omitted)

ndn.lua decodes this packet as:

Named Data Networking (NDN), LpPacket, Sequence: 4294967295, FragIndex: 0, FragCount: 2
    LpPacket, Type: 100, Length: 1478, Sequence: 4294967295, FragIndex: 0, FragCount: 2
        Sequence: 4294967295
        FragIndex: 0
        FragCount: 2
        Fragment, Type: 80, Length: 1456

In this packet, 51 08 00 00 00 00 00 53 54 0b is NDNLPv2 'Sequence' field. Its TLV-VALUE is 0x53540B (hex) or 5461003 (decimal).
But the dissector is showing a different sequence number.


Files

LpSeqNo.pcap (1.5 KB) LpSeqNo.pcap Junxiao Shi, 01/12/2018 10:56 AM
Actions #1

Updated by Junxiao Shi almost 6 years ago

  • Status changed from New to Code review
  • Assignee set to Junxiao Shi
  • % Done changed from 0 to 100
Actions #2

Updated by Junxiao Shi almost 6 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF