Bug #1720


Rewrite/redirect rules and URL encoding

Added by Anonymous almost 16 years ago. Updated almost 6 years ago.

Target version:


Dear lighty community,

I am using lighty to serve a wiki; to have nice urls, i use the following in my lighttpd.conf:

url.rewrite-once = ( "^/wiki/(.*)$" => "/wiki/awki.cgi/$1" )

and so i was hoping that everything going through /wiki/ would be interpreted by the script 'awki.cgi'. However, if I url-encode a part of the url, the above rewrite rule does not apply: if I ask my browser to access /wik%69/, lighty does not execute the script and gives me a
listing of files in that directory!

Is there a way to avoid that?
I asked in the forum last week but, as I had no answer, I decided to open a ticket; I apologize if this is unapropriate.

-- gaetan.bisson

Related issues 6 (0 open6 closed)

Related to Bug #1832: lighty doesn't quote spaces in urls in proxy moduleFixed2008-11-26Actions
Related to Bug #1827: 400 Response on any URL that countains a space character (ASCII 20)Fixeddarix2008-11-20Actions
Related to Bug #1819: mod_rewrite not working anymore after patchingFixed2008-11-11Actions
Related to Bug #1802: url-encode/decodeFixedstbuehler2008-10-20Actions
Related to Bug #911: Need for URL encoding in mod_redirect and possibly mod_rewriteFixedActions
Has duplicate Bug #1898: url.redirect matches the raw URL instead of the normalized URLDuplicate2009-02-12Actions
Actions #1

Updated by Anonymous almost 16 years ago

I've come up with the following workaround:

url.rewrite-once = ( "^/wiki/(.*)$" => "/wiki/awki.cgi/$1" )

$HTTP["url"] =~ "^/wiki" {
  $HTTP["url"] !~ "^/wiki/awki.cgi/" {
    url.access-deny = ("")

It works because the $HTTP["url"] condition is evaluated after the URL is parsed (so all url-encoded characters are hopefully replaced); well, unless I'm mistaken.

-- gaetan.bisson

Actions #2

Updated by hoffie almost 16 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

Should be fixed in r2278. Just for reference, in your case you consider this a security issue since it allows for unwanted disclosure of information.
Not sure if we are going to handle it as one, but I guess it should be at least noted.

stbuehler committed the fix and didn't close this ticket as trac was broken, so I'm doing that now. All kudos to him in any case. :p

Actions #3

Updated by stbuehler over 15 years ago

mod_redirect had similar problems:

Summary for now:
  • 1.4.x: fixed in r2278 (rewrite) and r2309 (redirect)
  • trunk: fixed in r2307 (rewrite) and r2310 (redirect)
Actions #4

Updated by stbuehler over 15 years ago

  • Status changed from Fixed to Reopened
  • Target version changed from 1.4.20 to 1.4.21
  • Patch available set to No

Patch(es) reverted in 1.4.x (r2362) - too many regressions came up.
See commit message for more details.

We are not sure yet what to do, maybe we won't fix this at all.

Actions #5

Updated by icy over 15 years ago

  • Target version changed from 1.4.21 to 1.4.22
Actions #6

Updated by stbuehler over 15 years ago

  • Target version changed from 1.4.22 to 1.4.23
Actions #7

Updated by stbuehler about 15 years ago

  • Target version changed from 1.4.23 to 1.4.x
Actions #8

Updated by gstrauss about 8 years ago

  • Related to Bug #911: Need for URL encoding in mod_redirect and possibly mod_rewrite added
Actions #9

Updated by gstrauss about 8 years ago

  • Status changed from Reopened to Need Feedback

con->request.uri is url-encoded and includes URI path and query-string
con->uri.path has been url-decoded and path has been simplified/normalized
con->uri.query is url-encoded

mod_rewrite operates on con->request.uri, meaning that there might be ways to subvert rewrite rules by url-encoding parts of it, since most rewrite rules will be against a normalized path and query string.

Perhaps the solution is to normalize the url-encoding of con->request.uri for rewrite rules, but there might still be complexities involved in virtual paths containing '.' or '..', PATH_INFO, whether or not to decode %2F ('/') in path and/or query-string parts, ...

I propose normalizing the url-encoding, including decoding %2F to '/'. Decoding %2F to '/' potentially loses some info in PATH_INFO and query string, but is a more secure default giving most people what they would expect. Maybe we could additionally provide a config switch to skip decode of %2F for the regex input.

Note: I am suggesting decoding con->request.uri temporarily for the regex match. If we were to normalize url-encoding at the start of the request, I would suggest leaving %2F url-encoded at that point of normalization. We might still decode %2F for regex matching, unless a new config flag were set.

(While discussing url-decoding here, please see url-encoding discussion of regex back-reference matches in #911)

Actions #10

Updated by gstrauss almost 6 years ago

  • Status changed from Need Feedback to Fixed
  • % Done changed from 0 to 100
Actions #11

Updated by gstrauss almost 6 years ago

See server.http-parseopts documentation for how to enable URL normalization (recommended)

For backwards compatibility, URL normalization is not enabled by default, though that may change in a future release.


Also available in: Atom