logoChat01.ai

pwn problem for you Obsidian Gate 395 Points Auth...

創建於：2026年7月20日

使用 GPT-5.6 Thinking 回答 Chat01

問題

pwn problem for you

Obsidian Gate
395 Points
Author
NomanProdhan

Beyond the obsidian gate lies a sealed archive.

Flag Format : BDSEC{s0mething_h3re}

*No Attachment Required. *

Alternative Server : nc 50.116.28.133 48271

Connection Info
nc 66.228.50.16 48271
Attempts

思考

undefined

思考

undefined

思考

The endpoint is still the blocker: repeated probes return immediate TCP refusal from both primary and alternative hosts, not a crash caused by input. Without a banner/menu or binary, there’s no observable attack surface to analyze yet.

Thought for 1m 22s

回答

I tested both endpoints at 2026-07-20 20:18 UTC:

text
66.228.50.16:48271   -> Connection refused
50.116.28.133:48271  -> Connection refused

This is an infrastructure failure, not an exploit crash—the TCP listeners are not running. Because Obsidian Gate has no downloadable attachment, the remote program’s banner and behavior are the only available attack surface. There isn’t enough information to construct a valid exploit or recover the flag while both servers reject every connection.

The competition is currently live, and the organizers direct participants to their Discord for event support. Their rules also prohibit brute-force and infrastructure scanning, so reporting the dead challenge service is the correct next step. (ctftime.org)

Send the organizers:

text
Obsidian Gate appears to be down. Both listed endpoints immediately return
“Connection refused”:

66.228.50.16:48271
50.116.28.133:48271

Confirmed at 2026-07-20 20:18 UTC. Could you please restart/check the challenge service?

After it is restored, capture the full initial interaction with:

bash
nc 66.228.50.16 48271 | tee obsidian_gate.txt

Paste the banner/menu and responses here; that should expose the intended vulnerability.

分享這個問答