CH4 — Default Admin
The management dashboard ships with default credentials — and once inside, there's no per-record authorization. Any account can read any account.
What Is the Open5GS WebUI?
Open5GS ships a WebUI management dashboard on port 3000. Operators use it to provision subscriber SIM cards, manage accounts, view network status, and configure the core. It is backed by MongoDB and exposes a REST API. The dashboard is the administrative control plane for the entire 5G core.
The WebUI ships with a hardcoded default administrator account: username admin,
password 1423. This is documented in the Open5GS source code and has been the default
since the project launched. In this lab, those credentials have never been changed.
A planted operator account in MongoDB has the flag in its note field — and the IDOR means
you do not even need admin privileges to read it.
Two Vulnerabilities
This challenge combines two distinct security failures that are each bad on their own — and catastrophic together. Understanding both is the point of the exercise.
Hardened OAM Interface
Your Lab (Open5GS)
The Attack
The moriah-mongodb container is accessible via docker exec from your jumpbox.
Query the accounts collection directly — this is the raw database the WebUI sits in front of,
and it has no access control of its own. The flag is in the note field of a planted operator account.
Direct MongoDB query (from your jumpbox SSH session)
MongoDB credentials are admin:moriah123. Query the open5gs database,
accounts collection, and filter for accounts with a non-empty note field.
http://<jumpbox-ip>:3000 lets you log in with admin / 1423 and browse accounts — but the browser UI does not render the note field. Use the MongoDB query above to retrieve the flag.
Real World Impact
Default credentials on management interfaces are one of the most extensively documented attack classes in telecommunications. Every major GSMA security advisory addresses them. They persist because operators treat lab-hardened software as production-ready without the hardening step.
-
OAM access equals full core control The Operations, Administration, and Maintenance interface is the highest-privilege plane in a 5G core. An attacker who logs into the WebUI as admin can provision new SIM cards, delete subscriber records, modify authentication keys, and reconfigure network functions — all through the same dashboard that legitimate operators use.
-
IDOR enables privilege escalation without privilege The IDOR vulnerability means an attacker does not need admin credentials — any valid account will do. If a lower-privileged helpdesk account is compromised, the IDOR allows reading every other account's data, including admin accounts and their internal notes. One credential becomes all credentials.
-
Vendor-documented defaults are public knowledge Default credentials are not secrets. They appear in product documentation, GitHub repositories, public forums, and CVE databases. An attacker targeting a specific 5G core vendor has a list of known defaults to try before attempting any brute force. Open5GS's admin/1423 is in its README.
-
Internal notes expose operational intelligence The note field exploited in this challenge mirrors a real pattern: operators store internal operational data — network segments, credentials for other systems, incident notes, customer information — in fields not intended for external access. IDOR makes all of it readable by any authenticated user.
Flag Format
The flag is in the
note field of the MongoDB account whose username begins with
ctf-ops-. Use the direct MongoDB query above — the browser UI does not display the note field.The note field contains the complete
TWIN{...} string — copy it exactly as shown and submit.
TWIN{...} format —
submit it exactly as it appears. The 32-character hex string inside the braces is the value to watch for.
If the note field is empty or missing, you may be querying the wrong database or the wrong collection.