There's many abusable url endpoints within Translate or at least there were recently, but when I tried to complain about it to Google, they just ignored it and said it's intended or whatever.
from what I can remember there's pure redirects and proxied translates pages, where the page will be under translate.google.com but show the malicious page and when you then click on stuff it can continue to the abusive page directly
but in general it takes Google eternities to do anything about abuse in their products from my experience
It doesn't for me at all. If I go to the URL I provided in the OP, the Google server responds with a 301 status code and Location header. Both when logged into a Google account and without logging in. Strange that it behaves in a different way (?) for you.
It will probably filter the URL through Google Safe Browsing, but that doesn't help much for phishing as they mostly use new or reputable domains, and browsers check that list on default settings anyway.
No notice for:
- Linux, Debian 12, Firefox - Linux, Gentoo, Waterfox - Linux, Mint, DuckDuckGo - iOS, DuckDuckGo - BSD, terminal, Lynx
Not to mention all the translate.google.com redirects that get indexed in Google, but Google says nothing is wrong and wontfix
Can you clarify what do you mean by that?
There's many abusable url endpoints within Translate or at least there were recently, but when I tried to complain about it to Google, they just ignored it and said it's intended or whatever.
from what I can remember there's pure redirects and proxied translates pages, where the page will be under translate.google.com but show the malicious page and when you then click on stuff it can continue to the abusive page directly
but in general it takes Google eternities to do anything about abuse in their products from my experience
I don't think Google would consider this an open redirect. It displays a notice and requires user interaction.
It doesn't for me at all. If I go to the URL I provided in the OP, the Google server responds with a 301 status code and Location header. Both when logged into a Google account and without logging in. Strange that it behaves in a different way (?) for you.
It will probably filter the URL through Google Safe Browsing, but that doesn't help much for phishing as they mostly use new or reputable domains, and browsers check that list on default settings anyway.
Using Vanadium on grapheneos and I get
"The page you were on is trying to send you to https://news.ycombinator.com/item?id=46613684.
If you do not want to visit that page, you can return to the previous page."
Doesn't show a notice or require user interaction for me.
Android, mobile Firefox.
Firefox 146 on Arch, no notice just got redirected right away.