VPN Security flaw... does this affect AirVPN?

[psychlops 26]

Does this affect us at all?

 

HUGE SECURITY FLAW LEAKS VPN USERS’ REAL IP-ADDRESSES...

 

http://torrentfreak.com/huge-security-flaw-leaks-vpn-users-real-ip-addresses-150130

 

From everything I know about AirVPN we're probably OK, but the question has to be asked.   

[OpenSourcerer 1360]

The individual user is at risk. There's also a thread covering this.

[iwih2gk 92]

Yet one more reason to be on a linux system!  Also, if you are employing a partition of trust with TOR (over Air) the TBB is set to eliminate that risk already.

 

I don't have a windows unit to do some tests with.

[S.O.A. 82]

Or a Mac. Just saying.

[YLwpLUbcf77U 32]

Holy cow.  IP Leak shows me as leak-free, but the test on the article had my real IP showing.  Making media.peerconnection.enabled to FALSE in FF fixed the issue right away.

[packetpuzzler 2]

Fix for Chrome users:

 

Adding the WebRTC Block Extension from the Chrome Store seems to fix the problem on Chrome (Windows 8.1).

 

Fix for Firefox users:

 

Type about:config” in the address bar. Scroll down to “media.peerconnection.enabled”, double click to set it to false.

[bobber6 8]

I am dissapointed , Why hasn't Air made its users aware of this huge security risk ?

 

even now , i don't see an anouncement from staff regarding this issue.

someone has started a thread in the off topic section, fine, but I think this issue is important enough to warrant a staff reaction on the front page.

Or at least in the announcement section of the forum.

 

 

It seems to have been known a long time; see this article from 12 September 2013 https://hacking.ventures/local-ip-discovery-with-html5-webrtc-security-and-privacy-risk/

I know it can be solved by setting "network lock" on, but before reading this yesterday i wasn't aware of this.

[LazyLizard14 11]

Not affected here since I use AirVPN on my pfsense router

[Staff 9761]

I am dissapointed , Why hasn't Air made its users aware of this huge security risk ?

 

even now , i don't see an anouncement from staff regarding this issue.

someone has started a thread in the off topic section, fine, but I think this issue is important enough to warrant a staff reaction on the front page.

Or at least in the announcement section of the forum.

 

 

It seems to have been known a long time; see this article from 12 September 2013 https://hacking.ventures/local-ip-discovery-with-html5-webrtc-security-and-privacy-risk/

I know it can be solved by setting "network lock" on, but before reading this yesterday i wasn't aware of this.

 

Hello!

When we have gathered all the data, we will make an announcement. In the meantime, last night we activated a check on ipleak.net pertaining to the issue. Note: only Windows systems with Firefox and Chrome with WebRTC peer connections enabled and Network Lock disabled seem to be affected so far, but we are still investigating.

 

Kind regards

[budweiser 2]

This ought to be a sticky right about now, untill the thing cools off. It is a nasty one. Everyone else should change all the settings!

[tranquivox69 25]

Hmmmm... I don't get it.

 

I checked and my Firefox has the media.peerconnection.enabled set to TRUE.

 

I then went to ipleak.net and saw the IP address of the AirVPN server I'm connected to.

 

Below I see:

 

Private IPv4 detected:

 

And two IP addresses. One is the address of my machine on the internal network (a 192.168.xxx.xxx one, to be clear) which obviously has no privacy impact, the other is an IP which doesn't appear to have anything to do with my ISP, as it's a iana.org address... why does that show up?

 

Edit: by using ipconfig /all I see that the "iana.org" address is the IPv4 Address of the TAP-Windows Adapter that gets installed by Open VPN. But it still does not have anything to do with my ISP...

 

Edit 2: after disabling media.peerconnection.enabled in FF and installing the WebRTC blocking extension for Chrome, I see the difference. No IP is read whatsoever. Without the modifications, though, from what I saw before, I would assume that while using AirVPN one wasn't leaking private information anyway (unless somebody has a use for my machine's local address, that is...).

[htpc 9]

Or a Mac. Just saying.

just so mac users don't believe they are safe from this. according to ipleak site my firefox and chromium installations on OSX both leaked my IPs. just saying!

[Staff 9761]

 

Or a Mac. Just saying.

just so mac users don't believe they are safe from this. according to ipleak site my firefox and chromium installations on OSX both leaked my IPs. just saying!

 

Hello!

 

Please provide at your convenience more info: OS X version, tested browsers in particular, thank you!

 

Kind regards

[Takanaka 0]

In the meantime, last night we activated a check on ipleak.net pertaining to the issue.

 

Came here to suggest this and it's already done. Glad I picked AirVPN as provider. Keep up the good work!

[Guest JWW]

Hmmmm... I don't get it.

 

I checked and my Firefox has the media.peerconnection.enabled set to TRUE.

 

I then went to ipleak.net and saw the IP address of the AirVPN server I'm connected to.

 

Below I see:

 

Private IPv4 detected:

 

And two IP addresses. One is the address of my machine on the internal network (a 192.168.xxx.xxx one, to be clear) which obviously has no privacy impact, the other is an IP which doesn't appear to have anything to do with my ISP, as it's a iana.org address... why does that show up?

 

Edit: by using ipconfig /all I see that the "iana.org" address is the IPv4 Address of the TAP-Windows Adapter that gets installed by Open VPN. But it still does not have anything to do with my ISP...

 

Edit 2: after disabling media.peerconnection.enabled in FF and installing the WebRTC blocking extension for Chrome, I see the difference. No IP is read whatsoever. Without the modifications, though, from what I saw before, I would assume that while using AirVPN one wasn't leaking private information anyway (unless somebody has a use for my machine's local address, that is...).

 

I had the same result and installed the Chrome extension resulting in 'No leak...' on ipleak. But I still don't fully understand the full implications, if any, of the results we both saw before. Are there any? Can someone enlighten me? 

[htpc 9]

 

 

just so mac users don't believe they are safe from this. according to ipleak site my firefox and chromium installations on OSX both leaked my IPs. just saying!

Or a Mac. Just saying.

Hello!

 

Please provide at your convenience more info: OS X version, tested browsers in particular, thank you!

 

Kind regards

 

osx yosemite 10.10.1 with firefox 35.0.1 and chromium 38.

[amazeballs 2]

Tried it on Safari using 10.10.2.  Doesn't seem to be affected.  Chrome and Firefox were though.  Did the suggested action for Chrome and it worked fine.  Just about to do the same for Firefox - I am quite surprised they haven't fixed this themselves yet, but never mind.

Interestingly, on Chrome and Firefox both didn't reveal my real IP before the fix, just some other IP in the UK.  I guess it is worth doing anyway though. 

[m0nk3n 0]

just add an app atleast for chrome to block webRTC detection. i added that in chrome and it doesnt show my real ip or dns address.

[waterfall 10]

Apparently WebRTCBlock does not work anymore for Chrome. Using ScriptSafe, also from the Chrome store, does block everything except my distant AirVPN server on ipleak.net though.