Tarnbeck is bookkeeping software. Its export page renders documents from named templates.
A saved June export failed while opening its template. This is the request the page sent.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Get the renderer to read a file that is not a template.
“A template name from the export page can only refer to a file in the templates directory.”
Accept a template ID and map it to a fixed server-side allowlist. If dynamic paths are required, resolve the path before opening it and verify it remains inside the templates directory. Return a generic error to the client, run the renderer with minimal file access, and add tests for traversal and encoded traversal values.
Check template loaders, downloads, translations, themes, export profiles, log viewers, and image endpoints. Look for request values joined to a server directory before a file is opened.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.