Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #10143

Closed
Open
Created Apr 18, 2016 by Administrator@rootOwner

Is gitlab vulnerable to a host header attack?

Created by: thestick613

GET /dashboard/ HTTP/1.1
Host: 1.2.3.4
X-Forwarded-Host: spoofed.com:443

will return

HTTP/1.1 302 Found
Server: nginx
Date: Thu, 17 Apr 2016 13:17:40 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 302 Found
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Location: http://spoofed.com:443/users/sign_in
Cache-Control: no-cache
Set-Cookie: _gitlab_session=xxxxxxxxxxxxxxxxxxxxxx; path=/; expires=xxxxxx; HttpOnly X-Request-Id: xxxxx
X-Runtime: 0.010452

Is this right? I'm using gitlab version 8.2.3-ce.0.

Assignee
Assign to
Time tracking