You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe finch should either sanitize paths properly or do not sanitize them at all.
E.g. /a/../b should produce the same result as /a/%2E%2E/b - either List(b) or List(a, .., b)
Since urlencoded path segments are weird but perfectly RFC-valid, I believe finch should not cut .. segments from the input.
Given route:
GET /../secret
prints"List(secret)"
but
GET /%2E%2E/secret
prints"List(.., secret)"
and
GET /%2F/etc/passwd
prints"List(/, etc, passwd)"
This can be nasty for unsuspecting people serving files from local disk
finch version:0.22.0
The text was updated successfully, but these errors were encountered: