Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 410
    • Issues 410
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #1730
Closed
Open
Issue created Mar 04, 2022 by ppom@ppomContributor

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