Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulnerability description and reproduction #1

Merged
merged 1 commit into from
Jun 9, 2021
Merged

Vulnerability description and reproduction #1

merged 1 commit into from
Jun 9, 2021

Conversation

mrbar42
Copy link
Contributor

@mrbar42 mrbar42 commented Jun 8, 2021

No description provided.

readme.md Outdated
### Exploitation
So, to exploit this we would need to create a STUN_BIND_REQUEST that will create a STUN_BIND_RESPONSE that has the 4in6 local ipv4 as XOR_MAPPED_ADDRESS.
First, we don't define any STUN server. When candidate pairing is done in that case, the STUN_BIND_REQUEST goes directly to the other peer.
Fortunately, the WEBRTC [network manager binds two UDP sockets](https://webrtc.googlesource.com/src/+/9f9bf38805e14688acef01fe6814b8ce3a98c09c/rtc_base/network.cc#284) - one on INADDR_ANY (0.0.0.0), and another on in6addr_any. These Sockets are used to create the local candidates, and also to do the MDNS protocol negotiation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are they also used to do the mDNS protocol negotiation ? I thought it's a different module. anyway not sure this explanation is relevant (what they are used for)

@shacharz shacharz assigned piroa and unassigned shacharz Jun 8, 2021
rephrase some text + add logo
@shacharz shacharz merged commit f129ecf into main Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants