$ cat writeup.md…
$ cat writeup.md…
sunshinectf2026
Task: Express/Node cookie-fabrication app where an inspector bot turns attacker ingredients into document.cookie writes; /api/seal awards a golden seal only when the bot's role cookie equals chief, but role=baker is HttpOnly and cannot be shadowed by JS. Solution: overflow Chromium's ~180-cookie-per-domain jar with ~250 padding ingredients to LRU-evict the HttpOnly role=baker, then a final role=chief ingredient becomes the effective role (session survives via Priority=High), yielding the golden seal and flag.
$ cat /etc/rate-limit
Rate limit reached (20 reads/hour per IP). Showing preview only — full content returns at the next hour roll-over.
CookieCorp is a custom-cookie fabrication service: design a batch of any ingredients you can dream up, submit it to our robotic Quality Inspector for a full inspection, and earn an official seal. Only the Chief can award the Golden Seal — the grand prize.
English summary: An Express/Node web app (nginx 1.24.0 front). A "baker" account
designs a batch of ingredients ({name,value} pairs). A headless-Chrome
"Quality Inspector" bot reviews the batch; client-side JS converts each
ingredient into a browser cookie and then asks the server to seal the batch. The
goal is to make the bot obtain the Golden Seal, which renders the flag on the
recipe page.
session cookie and an
HttpOnly role=baker cookie (both path=/)./builder): create a recipe with ingredients
[{name,value}] — up to 300 ingredients, name<=48, value<=64 chars.POST /api/recipe → returns a recipe id.POST /api/recipe/<id>/submit → queues the recipe for review./review/<id>, whose
HTML embeds window.__recipe = {...} and loads /static/js/mixer.js.For each ingredient the mixer executes:
document.cookie = name + '=' + value + '; path=/';
then calls:
fetch('/api/seal', { method: 'POST', credentials: 'same-origin', body: JSON.stringify({ recipeId }) });
So the attacker controls a set of cookies written into the bot's cookie jar.
...
$ grep --similar