Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 400
    • Issues 400
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhale
  • funkwhalefunkwhale
  • Issues
  • #1730
Closed
Open
Created Mar 04, 2022 by ppom@ppom

NGINX path traversal issue

In the default nginx configuration, those kinds of locations are used with alias directives:

location /_protected/music
location /_protected/media
location /front
location /front/embed.html

Therefore, a request like this could permit to escape the directory: /_protected/media../.. to /path/to/media/../../

To solve this issue, locations to directories should be suffixed with a / and locations to files should be prefixed with = as follows:

location /_protected/music/
location /_protected/media/
location /front/
location =/front/embed.html

Source: https://github.com/yandex/gixy/blob/master/docs/en/plugins/aliastraversal.md

Assignee
Assign to
Time tracking