Silverlink is a coalition loyalty scheme. Members can hold more than one account, and points can be moved between accounts they own.
You hold two: 88214009 with 41,000 points on it, and 90117442 with 2,500. This is the request the transfer screen sends.
Transfers are free, instant, and capped only by the balance on the sending account.
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. End up with more points than you started with.
“A transfer moves value between two records, so the two records are different.”
Reject a transfer where the source and destination are the same account, which is the cheap fix and the one to ship first. Then correct the underlying operation: apply both sides in one transaction with a conditional update on the balance, or express the debit and credit as relative adjustments rather than writes of a value read earlier, so that two updates to one row compose instead of overwriting.
Anywhere one operation reads and writes two records that the caller names: transfers between accounts, moving stock between locations, reassigning an item from one owner to another, merging two records, swapping two positions. The check is to put the same identifier on both sides and see whether anything objects, then look at whether the totals still add up.
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.