-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decode base64 parameters on strict blocked page #2832
Comments
Also, may users be able to toggle support for this feature on or off. |
I have a feeling this was requested before, but cannot find. |
|
Duplicate then? |
Yes, duplicate of #1784. Also: Maybe now |
But this issue is about decoding the parameter, not navigate to it. |
Yeah, I don't think this is related to |
I know, with trusted lists now we could have But this still applies: |
This was requested before, and I declined. Base64 is just one encoding, a server can set the encoding to anything, including proprietary ones, and supporting base64 would just open the door to be asked to support all sort of URL decoding. I prefer to decline. |
As one last comment on this thread, this can now be remedied using the new urlskip=
|
Prerequisites
I tried to reproduce the issue when...
Description
Let's say that you somehow accidentally clicked on an ad on Microsoft Edge's new tab page (example) and that you have
||bing.com/api/v1/mediation/tracking^$doc
in your personal filters. You'll be met with this screen:In this case, the value of the
rlink
parameter (the destination link) is not obfuscated in any way, as the advertiser is Microsoft themselves. For this one however, it's no longer the case:If we were to take the value of the
u
parameter and decode it from its base64 format, we get this:https%3a%2f%2fmonitor.clickcease.com%2ftracker%2ftracker.aspx%3fid%3dRpb1vHbW9FKx1e%26adpos%3d%26locphisical%3d166%26locinterest%3d%26adgrp%3d1332610468133218%26kw%3dwhat%2520is%2520inc%26nw%3da%26url%3dhttps%253A%252F%252Fwww.get.inc%252Fpromo%253Futm_source%253Dbing%2526utm_medium%253D%257Bmedium%257D%2526utm_campaign%253D%257BCampaignName%257D%2526utm_term%253Dwhat%252520is%252520inc%2526utm_content%253D%257Bcontent%257D%2526device%253Dc%2526geoloc%253D166%2526network%253Da%2526type%253Dsearch%2526utm_source%253Dbing%2526utm_medium%253Dcpc%2526utm_campaign%253D603204851%2526utm_content%253D1332610468133218%2526utm_term%253Dwhat%252520is%252520inc%2526kw%253Dwhat%252520is%252520inc%2526cpn%253D603204851%26cpn%3d603204851%26device%3dc%26ccpturl%3dget.inc%26pl%3d%26msclkid%3daecf13b8371b169014cb76b7a4b588c1
After percent-decoding this URL and then reducing it down to its components, we get this:
Now, the destination link is clearly visible: it's
https://www.get.inc/promo
.A specific URL where the issue occurs.
||bing.com/api/v1/mediation/tracking*
Steps to Reproduce
||bing.com/api/v1/mediation/tracking^$doc
u
parameter and decode it from its base64 format via this tool.Expected behavior
I expect uBO to parse the link in the second example this way:
Actual behavior
Feature not yet implemented at the time of writing
uBO version
1.52.2
Browser name and version
Operating System and version
The text was updated successfully, but these errors were encountered: