[Oblivious]

What is WebRTC?
WebRTC is an open framework for the web that enables Real Time Communications in the browser. It includes the fundamental building blocks for high-quality communications on the web, such as network, audio and video components used in voice and video chat applications.
These components, when implemented in a browser, can be accessed through a JavaScript API, enabling developers to easily implement their own RTC web app.
The WebRTC effort is being standardized on an API level at the W3C and at the protocol level at the IETF.

This is a crucial because even with a VPN your IP is still visable.
on Firefox type in about:config, change these settings:
  media.peerconnection.enabled = false
   media.peerconnection.turn.disable = true
   media.peerconnection.use_document_iceservers = false
   media.peerconnection.video.enabled = false
   media.peerconnection.identity.timeout = 1

to test if you are vulnerable to the WebRTC leak head over to this site
https://browserleaks.com/webrtc#webrtc-device-id

for Chrome:
    WebRTC in Google Chrome and Chromium-based web browsers is supported and enabled by default since Chrome version 23.
   To protect IP addresses from leaking, using the official webrtc.org extension WebRTC Network Limiter. It has few options, depending on what you're looking     for.

[mothered]

WebRTC was one of the first things I disabled when setting up my dedicated anonymity system.

It can also be disabled with ScriptSafe and NoScript Add-On for Chrome & Firefox respectively. For anonymity purposes, I don't use extensions and Add-Ons. Given WebRTC also relies on JavaScript, It's best to disable that too.

You've mentioned your IP can be leaked even when navigating with a VPN, which I certainly agree. It's not only your public/external/WAN IP that's of concern, but also your local/Internal IP (that's behind the LAN default gateway) Is exposed on the given device you're navigating with. Requests sent to STUN servers, also leak the IPs mentioned.

Nice contribution, thank you.

[Green Man]

for Chrome:
    WebRTC in Google Chrome and Chromium-based web browsers is supported and enabled by default since Chrome version 23.
   To protect IP addresses from leaking, using the official webrtc.org extension WebRTC Network Limiter. It has few options, depending on what you're looking     for.

As-well you should append " --disable-webgl " to the target for your chrome shortcut (on windows) to stop the webgl service.

Here is a demonstration of someone resolving your IP address. https://github.com/diafygi/webrtc-ips

Great post OP, spreading the awareness.  

[dismay]

If you're torrenting Game of Thrones, I wouldn't bother but if you are serious about anonymity -- give this a try.

[Drako]

Well, that was a useful thread because I literally had no idea this existed. I am wondering though, is this automatically disabled on TOR?

[darkninja1980]

for Chrome:
    WebRTC in Google Chrome and Chromium-based web browsers is supported and enabled by default since Chrome version 23.
   To protect IP addresses from leaking, using the official webrtc.org extension WebRTC Network Limiter. It has few options, depending on what you're looking     for.

Alternatively you could append " --disable-webgl " to the target for your chrome shortcut (on windows) to stop the webrtc service. Here is a demonstration of someone resolving your IP address. https://github.com/diafygi/webrtc-ips

Great post OP, spreading the awareness.  

thanks for adding the GitHub link.

[mothered]

I am wondering though, is this automatically disabled on TOR?

Tor does not support WebRTC.

[Nil]

The leak test did not display any of my address information even before following the steps. Hmm.

[Thib4ult]

This is interesting... thanks for the share!

[Yarrakk]

Thank you very much my friend