Skip to content

A hands-on security lab demonstrating secondary-context path traversal and DNS rebinding leading to SSRF

Notifications You must be signed in to change notification settings

Mgsy/lab-threadhub

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ThreadHub Lab

A hands-on lab for practicing the vulnerability chain described in SSRF: Breaking through hidden application context.

Demonstrates:

  • Secondary-context path traversal
  • DNS rebinding
  • SSRF

Note

To solve this lab, you'll need a domain that resolves to 127.0.0.1. You can use 127.0.0.1.nip.io - it automatically resolves to 127.0.0.1.


Scenario

ThreadHub is a SaaS platform for private team conversations. Each company (tenant) gets its own subdomain and can configure a custom enterprise domain for branding.

The platform offers:

  • Private threads between team members
  • Attachment system with ability to reference existing files
  • Custom domain configuration for enterprise customers

As a security researcher, your task is to test the application's security mechanisms.


Goal

Obtain the flag in format mgsy.dev{FLAG} from the endpoint:

http://127.0.0.1:8080/internal/config

Setup

1. DNS Configuration

Add entries to your hosts file:

Linux/macOS: /etc/hosts Windows: C:\Windows\System32\drivers\etc\hosts

127.0.0.1   threadhub.lab
127.0.0.1   acme.threadhub.lab

2. Start

docker compose up --build

Application: http://acme.threadhub.lab

Feedback

Did you enjoy the lab? Stuck on something? Have ideas for improvements or just want to share your experience? I'd love to hear from you - drop me a line at kacper@mgsy.dev

About

A hands-on security lab demonstrating secondary-context path traversal and DNS rebinding leading to SSRF

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published