Corrywell is an insurance broker. Claims handlers work in the portal all day; underwriting is a separate team with a separate area, and you are not on it.
Opening anything under underwriting gives you a refusal that does not look like the portal. Every other error in this application is JSON. This one is HTML, it carries X-Rule-Id: portal-underwriting, and it names no user, no role and no session.
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. Read the flagged quotes in the underwriting queue.
“A path rule written in front of the application matches the same set of requests the application routes.”
Authorise in the application, on the endpoint, against the actor. Where a path rule is genuinely the control, normalise the path before comparing it and make the comparison agree with the router: case-insensitive if the router is, and default-deny the prefix rather than denying one spelling of it. Add a test that requests the protected path in a different case and expects the same refusal.
Anywhere a path is compared in one component and routed in another: WAF and CDN rules, nginx location blocks, API gateway path policies, ingress rules, service mesh policies. The tell is a refusal that does not look like the application, and the check is to send the same path spelled differently and see whether the same thing answers.
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.