§1 Report sheetWL-2214 / Sample report

reset link could take over any customer account
Client | Regional insurer |
Test type | Web and API |
Scope | Customer portal, eight days. |
Findings | 1 Critical, 2 High, 6 Low |
Result | Account takeover |
Written for the client's board. The client is fictional and the name is withheld.
We tested the customer portal by hand for eight days, using test accounts the insurer set up for us.
The reset token was tied to the session of whoever requested it, and not to the account. Any customer account could be taken over.
Tokens are now single use and bound to the account. The retest confirmed it.
§3 TimelineWL-2214 / Sample report
Sample timeline, taken from the test log. Every action has a time.
When | Step | By |
Day 0 | Scope, test windows and stop contact signed | Lead |
Day 1 | Test accounts set up, sign-in and reset flows mapped | Tester |
Day 3 | Reset token tied to the wrong session | Tester |
Day 3 | Second test account taken over, proof saved | Tester |
Day 3 | Named contact phoned with the proof and a fix | Tester |
Day 8 | Remaining flows tested, testing ends | Tester |
After the test | ||
Day 8 | Report read through with the client on a call | Lead |
Day 12 | Tokens made single use and bound to the account | Client IT |
Day 38 | Retest: old links refused | Tester |
§4 FindingsWL-2214 / Sample report
Severity | Finding | Closed |
Critical | Reset token not bound to the account | Day 38 |
High | Reset tokens could be used twice | Day 38 |
High | No notice to the customer after a reset | Day 38 |
The other 6 stay in the client's copy.

§5 Client noteWL-2214 / Sample report
We read that reset code a dozen times in review. It took someone actually trying it to see the problem.
Tokens work once, for one account
Customers are told after every reset
Reset flows tested at each release
§6 More reportsEnd of WL-2214