Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint Security //

VPN

3/30/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

VPNs Are Still Leaking Your Personal Information

While VPNs are supposed to allow for safe, anonymous browsing, it turns out that STUN servers on the backend can still leak personal information and your whereabouts. Here's how to minimize that.

It has been found by a security researcher that almost one quarter -- 23% to be exact -- of current Virtual Private Networks (VPNs) will leak a user's true IP address due to a well-known, three-year-old vulnerability in a service that is enabled in most browsers by default.

However, let's start at the beginning.

WebRTC is open source software that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. Network, audio and video components used in voice and video chat applications can be simply built using WebRTC.

Session Traversal Utilities for NAT (STUN) servers are used to traverse networks by WebRTC. However, they are also used by VPNs when they execute the back-and-forth translation from a local home IP address to a new public IP address.

(Source: Flickr)
(Source: Flickr)

In January 2015, Daniel Roesler found that STUN servers will keep records of the user's public IP address and private IP address if the client is behind a NAT network, proxy or VPN client. Not only that, these servers will share this information with any other website if they had a WebRTC connection with a user's browser.

This means that it could be also used to de-anonymize and trace users behind common privacy protection methods such as a VPN, SOCKS Proxy, or HTTP Proxy. Tor users were also found to be vulnerable to tracking from this method before hardening was done.

Browser makers attempted to somewhat mitigate the problem, but most left WebRTC active in the end.

Still, browsers that have WebRTC running by default include Brave, Mozilla Firefox, Google Chrome, Internet (Samsung Browser), Opera, and Vivaldi. The Tor Browser, Microsoft Edge, and Internet Explorer do not enable by default.

Paolo Stagno wanted to see if the situation with WebRTC and VPNs had changed. He did some testing and posted the results on his blog. He found that VPNs from several vendors were still leaking local IPs if a browser had WebRTC active.

In his post, Stagno admits he didn't test every VPN out there and asked his readers to contribute their own results from other VPNs when they went to a WebRTC test page that he set up.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

Stagno gives these tips for anonymous surfing:

  • Disable WebRTC
  • Disable JavaScript (or at least some functions. Use NoScript)
  • Disable Canvas Rendering (Web API)
  • Always set a DNS fallback for every connection/adapter
  • Always kill all your browsers instances before and after a VPN connection
  • Clear browser cache, history and cookies
  • Drop all outgoing connections except for VPN provider

Another method might be to establish the VPN connection from your local router to it, rather than directly from your computer.

VPNs may not be as secure as users would like to think. Unless there is perfect end-to-end security, information may still leak out.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-21392
PUBLISHED: 2021-04-12
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.28.0 requests to user provided domains were not restricted to external IP addresses when transitional IPv6 addre...
CVE-2021-21393
PUBLISHED: 2021-04-12
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.28.0 Synapse is missing input validation of some parameters on the endpoints used to confirm third-party identif...
CVE-2021-29429
PUBLISHED: 2021-04-12
In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by Gradle. Some builds could be vulnerable to a local information disclosure. Remote files accessed through TextResourceFactory are downloaded in...
CVE-2021-21394
PUBLISHED: 2021-04-12
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.28.0 Synapse is missing input validation of some parameters on the endpoints used to confirm third-party identif...
CVE-2021-22497
PUBLISHED: 2021-04-12
Advanced Authentication versions prior to 6.3 SP4 have a potential broken authentication due to improper session management issue.