Edge may generate wrong ICE Binding requests (wrong USERNAME length)

Duplicate Issue #12332512 • See Issue #12332457

Details

Author
Iñaki B.
Created
Jun 13, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Duplicates
See progress on Bug #12332457
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When connecting Edge to Jitsi-videobridge (JVB) I’ve found that, very often, ICE fails. This is because JVB replies 401 with Wrong MESSAGE-INTEGRITY error to some Binding requests sent by Edge.

The issue is fully reported here (Wireshark traces included):

https://github.com/jitsi/lib-jitsi-meet/issues/498

The most interesting comment in that issue is the latest one, in which a Jitsi developer has found out that some of those ICE Binding requests from Edge may have a wrong length value for the USERNAME attribute, producing the above error (screenshots attached):

https://github.com/jitsi/lib-jitsi-meet/issues/498#issuecomment-308260513

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Shijun S.”

    Changed Status to “Confirmed”

  • While reporting this issue, the submit action failed several times (that’s why there is a duplicated issue #12332496).

    I’ve also realized that, during the submit process, one of the attachments was lost. I’ve added it right now to the issue, so you can compare two binary ICE Binding Requests with same USERNAME but obvious different padding (at binary level). On of them is causing the WRONG MESSAGE-INTEGRITY error in the receiver.

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “Duplicate”

  • This bug has marked as duplicate. Please follow the parent issue to get new updates.

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

Sign in