-
Notifications
You must be signed in to change notification settings - Fork 61
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
Private pages can be overriden by URL hacking #44
Comments
I just stumbled upon this issue while setting up gollum with omnigollum. Also having the described problem, I finally was able to solve this using regular expressions in the :protected_routes => [
/\/[Pp][Rr][Ii][Vv][Aa][Tt][Ee]\/.*/,
/\/[Pp][Rr][Ii][Vv][Aa][Tt][Ee]/
] I'm sure this solution can easily be improved, but being no ruby coder, this was the best I could come up with. Anyway, maybe this helps. |
While it is good that @ctreffe found a workaround, this is basically a (fairly major) security issue in omnigollum code. Any chance this is going to get fixed? |
@mvdkleijn It's not a security flaw in omnigollum. There is no way to turn off case sensitive route matching in Sinatra (that I could find, please correct me if I'm wrong). So you have two options. Perform URL normalisation on the web server, or use case insensitive regexes demonstrated above. I wouldn't necessarily write them like that though. Assuming ruby is smart enough to not treat |
If you want to confirm it does, I'll add some notes to the readme. Note that the default endpoints that omnigollum protects ARE case sensitive, and so the default globbing style patterns work fine. |
I stand corrected. It is a "feature" of Sinatra indeed. 😄 |
I think the case-sensitivity issue is no longer a live one since gollum 5.x, since we're now matching all routes (not just 'special' routes such as |
Thanks for your great work on Omnigollum.
While using it, I've just noticed that if you specify
protected_routes
for Omnigollum in Gollum'sconfig.rb
as such:Then if you go to e.g. https://mywiki.com/private the authorization prompt is shown as expected. However, there seems to be an easy way to override this:
I'm by no means a Ruby developer, so I'm not too sure what's going on behind the scenes.
protected_routes
is processed here: https://github.com/arr2036/omnigollum/blob/master/lib/omnigollum.rb#L311Something I tried was to modify the route, so that it's converted to downcase. While that works for that particular case, then unauthenticated users cannot access the open parts of the site that use capital letters, e.g. mywiki.com/Home. So no, the workaround does not quite work:
I'm sure there are better and cleverer ways to fix this.
Thanks.
The text was updated successfully, but these errors were encountered: