Saltwick hosts engineering workspaces. You administer Ferrymead, a workspace owned by Northwood Group.
You can change most security settings. The two-factor toggle is greyed out and labelled managed by Northwood Group. A policy service checks each update before the workspace service saves it.
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. Stop two-factor being enforced on Ferrymead.
“Every component that reads a JSON body will choose the same value when a key appears more than once.”
Parse the request body once and reject duplicate keys before running policy checks. Pass that parsed object to the workspace service instead of parsing the raw body again. Add an integration test that sends a protected field twice.
Check requests that pass through gateways, middleware, signature checks, or separate services. Duplicate JSON keys, headers, query parameters, and form fields can bypass a control when two components choose different values.
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.