MS Edge ICE problem - wrong encoding of USERNAME?

Issue #7728575 • Assigned to Travis L.

Details

Author
Erik L.
Created
May 29, 2016
Privacy
This issue is public.
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Weird ICE behaviour during interoperability testing of ORTCLib with MS Edge.

During ICE connectivity checks, Edge side seems to be sending 2 different Binding Requests to the remote side - first one contains proper length of USERNAME (0x0006) and CANDIDATE-IDENTIFIER (0x8054) attributes, while second one is adding the number of padding bytes to the length value. This causes the username to be mis-interpreted to include NUL bytes.

Please find both full Stun Binding request messages bellow:

  1. Message with proper length
    00 01 00 60 21 12 a4 42 5f 92 41 8e 05 3a bf ed 9f 88 c0 72 00 06 00 15 51 6d 54 70 74 31 59 36 61 31 70 30 48 54 6b 76 3a 32 74 66 41 00 00 00 00 24 00 04 6e ff fe ff 80 29 00 08 00 00 00 00 14 f1 a9 53 80 54 00 01 31 00 00 00 80 70 00 04 00 00 00 03 00 08 00 14 4c 0a b1 97 1e ce f1 1a ad c7 d7 a5 35 39 9f 9a 47 c6 b5 29 80 28 00 04 2c ba c5 cf

Message with wrong length (padding bytes included) 00 01 00 60 21 12 a4 42 5f 92 41 8e 05 3a bf ed 9f 88 c0 72 00 06 00 18 51 6d 54 70 74 31 59 36 61 31 70 30 48 54 6b 76 3a 32 74 66 41 00 00 00 00 24 00 04 6e ff fe ff 80 29 00 08 00 00 00 00 14 f1 a9 53 80 54 00 04 31 00 00 00 80 70 00 04 00 00 00 03 00 08 00 14 53 b8 52 43 d9 7c 6d 0a 19 81 6f 21 7b 4e 31 2a 88 73 e9 c5 80 28 00 04 99 7c 91 54

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Travis L.”

    • We just ran into this as well… the USERNAME is coming in padded with NULLs throwing off the username comparison.

    You need to sign in to your Microsoft account to add a comment.

    Sign in