Pipe 107DK In 2016 the WebRTC bug is still exposes user's private IP information

In 2016 the WebRTC bug is still exposes user's private IP information

by
Anonymous Coward
in security on (#107DK)
It is now 2016. Why isn't the WebRTC privacy bug fixed in Chrome? How long can VPN users expect for their private information to be accessible when using the Chrome browser using the STUN based attack? This fault in WebRTC exposes the private LAN IP information and actual IP address of users utilising a VPN service.
score 0
  • Closed (timeout)
Reply 1 comments

How to disable it (Score: 0)

by Anonymous Coward on 2016-04-22 04:55 (#1BCHP)

https://www.ivpn.net/knowledgebase/158/My-IP-is-being-leaked-by-WebRTC-How-do-I-disable-it.html

Firefox:
Type about:config in the browser's address bar and hit enter.
Confirm you will be careful if the prompt appears.
Search for media.peerconnection.enabled.
Double-click the preference to set it to false.

See also: https://diafygi.github.io/webrtc-ips/

Use https://ipleak.net/ to see if you are affected. VPN users should take note.