Bug #15835

Path traversal symlink - WEBrick

Added by Dhiraj (Dhiraj Mishra) over 1 year ago. Updated over 1 year ago.

Target version:


A path traversal issue was observed in WEBrick ( WEBrick/1.4.2 (Ruby/2.6.3/2019-04-16)) via symlink. WEBrick serves static page for the current directory once enabled, however using symlink attacker could view data outside the hosted/running directory.

Steps to reproduce:

mkdir nothing
cd nothing
ln -s ../../ symlnk
ruby -run -ehttpd . -p8080

This would allow the attacker to view sensitive data outside the root/running directory.

We can probably educate users about this behavior in the WebBrick documentation and providing a flag/parameter to disable/enable following symlinks.

Updated by naruse (Yui NARUSE) over 1 year ago

  • Status changed from Open to Feedback

On Apache with FollowSymLinks enabled, it can traverse out of DocumentRoot.
Therefore it's not a problem.

Updated by shevegen (Robert A. Heiler) over 1 year ago

While I agree with naruse, it may be worthwhile to mention this briefly at e. g. - it could still surprise
users so it could be useful to mention it; perhaps at the section "WEBrick can be run
as a production server for small loads.".

As writing documentation is always a bit tedious, I will try my luck with a slight
modification to it here, from:

"WEBrick can be run as a production server for small loads. Be aware that symlinks
might allow users to view data outside of the designated root directory, such as
for the Apache webserver with the FollowSymlinks option enabled".

Not sure if this is great but I just wanted to provide a bit of text - perhaps it
can help others adapt it and write an improved documentation; it's just a suggestion.


Updated by jeremyevans0 (Jeremy Evans) over 1 year ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF