Page MenuHomePhabricator

Possible to circumvent shortening URL list by Special:Search
Closed, DeclinedPublic


For example, redirects to Google. This is completely unacceptable as it's possible to first redirect the link to wmflabs, where arbitrary codes can be added, and than redirect to arbitrary site.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 4 2016, 5:57 AM

What's the completely unacceptable part? You're discussing the difference between redirecting to versus having a regular hyperlink to on any of our sites?

This may also be a problem of Special pages as users may use this to circumvent spam blacklist.

Possible solution:

  1. Show a page with "You are redirected to a non-Wikimedia site. This site may contain malware or other inappropriate content." when using Special:Search with non-forwarded interwiki prefixes
  2. Use POST instead of GET for search box when JavaScript enabled (as this can also be circumvented by

Right. The new part here seems to be that you can have a "" short URL. Is that correct? If so, is that really so different from a user putting a regular hyperlink such as on a wiki page for users to click? It seems like we're only talking about a single extra hop.

Vaguely related: and

Currently URLs such as give a response similar to this:

$ curl -I ""
HTTP/1.1 302 Found
Date: Thu, 04 Aug 2016 06:06:43 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Server: mw1213.eqiad.wmnet
X-Powered-By: HHVM/3.12.1
X-Content-Type-Options: nosniff
P3P: CP="This is not a P3P policy! See for more info."
Vary: Accept-Encoding,X-Forwarded-Proto,Cookie,Authorization
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Backend-Timing: D=36893 t=1470290803175909
X-Varnish: 1282349625, 313197216
Via: 1.1 varnish, 1.1 varnish
Accept-Ranges: bytes
Age: 0
X-Cache: cp1067 pass, cp1052 pass
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Set-Cookie: WMF-Last-Access=04-Aug-2016;Path=/;HttpOnly;secure;Expires=Mon, 05 Sep 2016 00:00:00 GMT
X-Analytics: https=1;nocookies=1
X-Client-IP: 2601:146:c902:86af:9158:42c4:bc4b:41c
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Set-Cookie: GeoIP=:::::v6; Path=/; secure;

We could check that the target URL is HTTP 200 (i.e., not HTTP 301 or HTTP 302), but implementing such a check may create its own set of challenges.

The shortening URL list is useless if you can make short URL which are eventually redirected to arbitrary site.

Legoktm set Security to Software security bug.Aug 4 2016, 7:05 AM
Legoktm added a project: Security.
Legoktm changed the visibility from "Public (No Login Required)" to "Custom Policy".
Legoktm added a subscriber: Legoktm.

I would kindly ask that if you think you've found a vulnerability in a *deployed* extension, that you file it as a security bug.

Legoktm closed this task as Declined.Aug 4 2016, 7:20 AM

There is no issue here in UrlShortener that I see. You could have already redirected someone offsite using Special:Search or one of the other pages that does interwiki redirects. UrlShortener might obfuscate the target a bit, but you could have probably done that in another way.

T122209: Special:Search allows redirects to any interwiki link tracks fixing the external redirect stuff, so I'm going to close this as declined, but leave it private until that one becomes public.

@Legoktm Can you let me subscribe that task? I want to find what things happen.

Also I have filed another task about circumventing shortening URL list (also security bug), named T142071: Disable Forward to non-WMF sites in interwiki data

T122209: Special:Search allows redirects to any interwiki link tracks fixing the external redirect stuff, so I'm going to close this as declined, but leave it private until that one becomes public.

The other task is public now, going to unseal this one given it is about the same thing.

Urbanecm changed the visibility from "Custom Policy" to "Public (No Login Required)".Dec 9 2019, 8:04 AM