uBlock Origin v1.25.0 new feature cause DNS leaks.

Question

uBlock Origin v1.25.0 new feature cause DNS leaks.

Closed this issue 5 years ago · 22 comments

Prerequisites

I verified that this is not a filter issue
- Filter issues MUST be reported at filter issue tracker
This is not a support issue or a question
- Support issues and questions are handled at /r/uBlockOrigin
I performed a cursory search of the issue tracker to avoid opening a duplicate issue
- Your issue may already be reported.
I tried to reproduce the issue when...
- uBlock Origin is the only extension
- uBlock Origin with default lists/settings
- using a new, unmodified browser profile
I am running the latest version of uBlock Origin
I checked the documentation to understand that the issue I report is not a normal behavior

Description

Hello there, I notice that uBlock Origin v1.25.0 have a new way to block 1st-party tracking. This problem is related to #780.

Let me explain a little bit of background first. To protect my privacy, I use a socks5 proxy to surfing the internet. I setting a manual proxy configuration on my Firefox and check the box "Proxy DNS when using SOCKS v5". It shouldn't have any UDP DNS traffic, but it happened (sudo tcpdump udp can confirm it.).

It makes me pretty annoying that It exposed my real location and the ISP will know what I browse. I wonder if it's a bug of Debian Firefox ESR. So I download the latest Firefox stable, the problem was gone. Then I switch to old Firefox profile, the problem back again. So I suspect some extensions may cause. Finally, I found it is uBlock Origin cause UDP DNS traffic. I remember that it requires IP/Hostname permission after yesterday upgrade.

A specific URL where the issue occurs

No specific URL.

Steps to Reproduce

It required a socks5 proxy. Torbroswer provides the free socks5 proxy. The first thing is to download the TBB from Torproject website.
Setting the socks5 proxy for Firefox. (TBB is listen on 127.0.0.1:9150)
Using the DNS leaks test service like:

https://ipleak.net/
https://dnsleaktest.com/
http://whatismydnsresolver.com/
You can find the "DNS leaks" exposed your location. Meanwhile, it could use tcpdump udp to look realtime UDP DNS traffic, it can be confirmed it happened. Disable the uBlock Origin, the problem is gone.

Expected behavior:

It shouldn't be any UDP DNS traffic if you setting the socks5 proxy on Firefox.

Actual behavior:

UDP DNS traffic happened when I setting the socks5 proxy on Firefox, even I check the box "Proxy DNS when using SOCKS v5".

Your environment

uBlock Origin version: uBlock Origin v1.25.0 from AMO
Browser Name and version: Firefox 73.0.1 (64-bit)
Operating System and version: GNU/Linux Debian

Answer 1 · 2020-02-26T12:58:30.000Z

I think uBlock Origin shouldn't check the DNS CNAME record when users setting their proxy configure on Firefox.

Answer 2 · 2020-02-26T13:01:37.000Z

uBO just makes use of the browser.dns API. If you think the API is doing something wrong that disregard OS- or Firefox-side settings which you think should not be disregarded, you will have to file an issue with Firefox.

You can disable uBO's canonical name-uncloaking from advanced settings if you do not like the feature.

Answer 3 · 2020-02-26T15:11:52.000Z

Okay, ~~It's nothing could do with Firefox either, because socks5 doesn't support DNS forwarding~~ (I'm not pretty sure). So Firefox will use local DNS. The only thing could I do is enable DoH feature and set network.trr.mode=3. Maybe uBlock should write a document about it. It is a real side effect on the new feature (to some users). @gorhill

Edited: I open a thread on bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1618271

Answer 4 · 2020-03-22T08:09:31.000Z

Recently I notice DNS leaks too. I looked everywhere and finally found uBlock Origin. Even this is unavoidable or broken because the browser API I think uBlock Origin should make people aware of this issue.

BTW why isn't uBlock Origin using the offline option like Flagfox?

Answer 5 · 2020-03-22T13:08:06.000Z

@lilydjwg Is your setup similar to OP, i.e. using a socks5 proxy?

Answer 6 · 2020-03-22T13:34:08.000Z

@gorhill I use a PAC file to proxy part of my requests, and some of them are proxied to a socks5 proxy. Flagfox will show that it doesn't have the DNS information on proxied websites.

I saw some DNS requests for domains that should have gone to the proxy and after some observation I found uBlock Origin was doing this. Setting cnameUncloak: false makes those unintended DNS requests go away.

Answer 7 · 2020-03-22T14:46:13.000Z

@lilydjwg From your profile, it seems you would be able to use the debugger to step into uBO's code?

If so, I would be curious to find out whether the proxyInfo property is set when uBO's onHeadersReceived listener is called.

My thinking is that uBO could maybe avoid using browser.dns.resolve() if it is able to detect that the network requests are proxied -- at least until 1618271 is resolved.

Answer 8 · 2020-03-22T15:12:19.000Z

@gorhill Yes it's set and proxyDNS is true.

Edit: I mean it's set when the request is proxied (all properties seem ready). It's null if not proxied.

Answer 9 · 2020-03-22T17:32:28.000Z

BTW why isn't uBlock Origin using the offline option like Flagfox? [...] Flagfox will show that it doesn't have the DNS information on proxied websites.

I am also a user of Flagfox, notice that it doesn't cause DNS leaks. Reading the code finding that it uses offline flag. After I try this idea, I don't think it could work in this case, because it won't have any DNS CNAME record cache before uBlock request (unlike DNS A/AAAA record in Flagfox case).

Answer 10 · 2020-03-22T17:36:01.000Z

What Flagfox does is not applicable to uBO -- uBO uses the API in a blocking manner, i.e. the dns.resolve() API is used while the network request is held back until an answer arrive. In Flagfox, the dns.resolve() is used to observe only, not in a blocking manner.

Answer 11 · 2020-03-22T19:27:01.000Z

In the latest dev build, 1.25.3b7, uBO will automatically disable cname-uncloaking when it detects that requests are proxied. To find out if this work as intended, you will of course need to put back cnameUncloak to its default value of true.

Feedback appreciated.

Answer 12 · 2020-03-23T05:09:28.000Z

I still have the problem in uBlock Origin v1.25.3b7.

Settings

Setup a socks5 proxy on Firefox 74.0.
network.proxy.socks_remote_dns=true in about:config (same proxyDNS: true as @lilydjwg)
network.trr.mode=0 in about:config
cnameUncloak: true, cnameUncloakProxied: false in uBO advanced settings

What I see

I open the https://ipleak.net/ and doing some test. Using tcpdump to capture UDP DNS traffic, I still see something like follow (tomacat is my machine's hostname):

$ sudo tcpdump udp port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlp3s0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:50:07.166089 IP tomacat.37560 > _gateway.domain: 11448+ A? nwv5dyztu6o1o7xg5yp8nmr0dnqyf48qw32pzslo.ipleak.net. (69)
12:50:07.166111 IP tomacat.37560 > _gateway.domain: 23238+ AAAA? nwv5dyztu6o1o7xg5yp8nmr0dnqyf48qw32pzslo.ipleak.net. (69)
12:50:07.167239 IP tomacat.39124 > _gateway.domain: 46747+ A? g15hezrsl41pg2n3xice1chrvkbpwzr8k2fo68k1.ipleak.net. (69)
12:50:07.167252 IP tomacat.39124 > _gateway.domain: 35495+ AAAA? g15hezrsl41pg2n3xice1chrvkbpwzr8k2fo68k1.ipleak.net. (69)
12:50:07.168623 IP tomacat.53883 > _gateway.domain: 7761+ A? soycqomnr363xhy64o4vgskbbhszu1aowji5ekeb.ipleak.net. (69)
12:50:07.168638 IP tomacat.53883 > _gateway.domain: 1628+ AAAA? soycqomnr363xhy64o4vgskbbhszu1aowji5ekeb.ipleak.net. (69)
12:50:07.571706 IP _gateway.domain > tomacat.37560: 11448 1/0/0 A 95.85.16.212 (85)
12:50:07.571720 IP _gateway.domain > tomacat.53883: 7761 1/0/0 A 95.85.16.212 (85)
12:50:07.571728 IP _gateway.domain > tomacat.43213: 61608 1/0/0 A 95.85.16.212 (85)
12:50:07.571735 IP _gateway.domain > tomacat.43213: 3763 1/0/0 AAAA 2a03:b0c0:0:1010::509:d001 (97)
12:50:07.572258 IP tomacat.53185 > _gateway.domain: 35947+ A? zaqyly2w67351l9ks4dq52wa3eggjh41xejzn663.ipleak.net. (69)
12:50:07.572272 IP tomacat.53185 > _gateway.domain: 52853+ AAAA? zaqyly2w67351l9ks4dq52wa3eggjh41xejzn663.ipleak.net. (69)
[...]

Then I setting cnameUncloak: false, the problem gone again. (Test on both my Firefox old profile and new profile.)

Answer 13 · 2020-03-23T05:12:45.000Z

I'm afraid that it didn't work. I still observe the same DNS leak.

Answer 14 · 2020-03-23T13:45:16.000Z

Setup a socks5 proxy on Firefox 74.0.

I don't have a proxy provider. Is there a way for me to test this on my side?

Answer 15 · 2020-03-23T14:38:05.000Z

I don't have a proxy provider. Is there a way for me to test this on my side?

Tor browser provide one, it is listen on 127.0.0.1:9150.

Steps

Start Tor browser and make it connect to Tor network. (shouldn't be hard.)
Start the Firefox as following prefs:

user_pref("network.proxy.type", 1);
user_pref("network.proxy.socks", "127.0.0.1");
user_pref("network.proxy.socks_port", 9150);
user_pref("network.proxy.socks_remote_dns", true);

(Edited: I can't reproduce on Tor Browser itself, I think TBB may have some security hardening on this side.)

Answer 16 · 2020-03-23T16:22:44.000Z

@tomac4t Great, this works for testing purpose -- I already had the Tor browser installed. So anyways now that I could test the code path I see that there is a typo in the code. I will publish a fix asap.

Answer 17 · 2020-03-24T02:00:09.000Z

03/24/2020: After trying uBlock Origin v1.25.3b8, ~~I didn't observe UDP DNS traffic anymore when the proxy is set up on Firefox.~~ I observe UDP DNS from my firefox again (old profile with Firefox 74), after restarting the firefox then the situation disappear. If there is further information, I will append here. I still can't reproduce it on new profile of Firefox Developer (75.0b7) with lastest uBO (fe0c2c). Everything works great.

I also test the case when setting a proxy with an add-on like SwitchyOmega. PAC (Automatic proxy configuration, which @lilydjwg comment above) case I didn't test, because I don't familiar with it. But I think it also could work.

03/25/2020: Firefox 74.0 with uBlock Origin v1.25.3b9 works fine.

Answer 18 · 2020-03-25T09:05:11.000Z

I don't see leaked DNS queries now but I'm still monitoring.

Answer 19 · 2020-03-30T23:12:50.000Z

its still leak with latest ublock origin 1.25.3rc0, when check use https://www.expressvpn.com/dns-leak-test

Steps to Reproduce
install dan start browsec https://addons.mozilla.org/en-US/firefox/addon/browsec/ or hoxx vpn https://addons.mozilla.org/en-US/firefox/addon/hoxx-vpn-proxy/

use DNS leaks test site
https://www.expressvpn.com/dns-leak-test

but when check use https://dnsleaktest.com/, doesn't leak

Answer 20 · 2020-04-09T11:33:23.000Z

FF 68.6.1esr and uBO 1.26.0 works as intended. Cname lookup is disabled when browser is proxied. And enabled when not.

Also I find that http://browserleaks.com/dns gives the most correct results. It resolves 100 randomly generated domain names asynchronously, 50 with A record (IPv4-only) and 50 with both A and AAAA records. And does so really fast compared to the other tests.

Orbot on android with FF 68.6.0esr and uBO 1.26.0 does some magic with the "vpn" feature and uBO doesn't detect browser is proxied and Cname lookup works. That with no dns leakage.

Before uBO 1.26.0 I made a script that cleared /etc/resolv.conf and Cname lookup stopped working on uBO 1.25.2, further prooving the FF bug.

I really hope FF devs fix the bug since Cname lookup is a cool feature in uBO. When uMA gets it I hope it also have the fix from uBO to disable it on proxied browsers until FF is fixed.

Thank you gorhill for the awesome work with both extensions.

Answer 21 · 2020-04-09T12:27:20.000Z

When uMA gets it I hope it also have the fix from uBO to disable it on proxied browsers until FF is fixed.

CNAME uncloaking is already present in the dev build of uMatrix, the workaround added in uBO however is not, so you might reproduce it with uMatrix dev build.

Answer 22 · 2020-04-10T05:10:24.000Z

@tomac4t

Prerequisites

I verified that this is not a filter issue

Filter issues MUST be reported at filter issue tracker

This is not a support issue or a question

Support issues and questions are handled at /r/uBlockOrigin

I performed a cursory search of the issue tracker to avoid opening a duplicate issue

Your issue may already be reported.

I tried to reproduce the issue when...

uBlock Origin is the only extension

uBlock Origin with default lists/settings

using a new, unmodified browser profile

I am running the latest version of uBlock Origin

I checked the documentation to understand that the issue I report is not a normal behavior

Description

Hello there, I notice that uBlock Origin v1.25.0 have a new way to block 1st-party tracking. This problem is related to #780.

Let me explain a little bit of background first. To protect my privacy, I use a socks5 proxy to surfing the internet. I setting a manual proxy configuration on my Firefox and check the box "Proxy DNS when using SOCKS v5". It shouldn't have any UDP DNS traffic, but it happened (sudo tcpdump udp can confirm it.).

It makes me pretty annoying that It exposed my real location and the ISP will know what I browse. I wonder if it's a bug of Debian Firefox ESR. So I download the latest Firefox stable, the problem was gone. Then I switch to old Firefox profile, the problem back again. So I suspect some extensions may cause. Finally, I found it is uBlock Origin cause UDP DNS traffic. I remember that it requires IP/Hostname permission after yesterday upgrade.

A specific URL where the issue occurs

No specific URL.

Steps to Reproduce

It required a socks5 proxy. Torbroswer provides the free socks5 proxy. The first thing is to download the TBB from Torproject website.

Setting the socks5 proxy for Firefox. (TBB is listen on 127.0.0.1:9150)

Using the DNS leaks test service like:

https://ipleak.net/

https://dnsleaktest.com/

http://whatismydnsresolver.com/
You can find the "DNS leaks" exposed your location. Meanwhile, it could use tcpdump udp to look realtime UDP DNS traffic, it can be confirmed it happened. Disable the uBlock Origin, the problem is gone.

Expected behavior:

It shouldn't be any UDP DNS traffic if you setting the socks5 proxy on Firefox.

Actual behavior:

UDP DNS traffic happened when I setting the socks5 proxy on Firefox, even I check the box "Proxy DNS when using SOCKS v5".

Your environment

uBlock Origin version: uBlock Origin v1.25.0 from AMO

Browser Name and version: Firefox 73.0.1 (64-bit)

Operating System and version: GNU/Linux Debian

SOCKS5 does in fact utilize UDP in addition to TCP (which was the sole protocol used in its previous - SOCKS4 - iteration. Please keep that in mind & block UDP connections - in/out -on :9150.
In relation to DoH which you alluded to in #911 (comment) - I strongly advise against it if you're convened about privacy. Opt instead for DoT or DNSCrypt.

Peace.