researcher@authorized-scope:~$ list ./findings

Bug Bounty Research

Evidence-led case studies and independent technique guides. Case studies retain their stated triage outcomes; technique guides use synthetic examples and disclose no live target.

4 case studies 3 technique guides Clear evidence boundaries

Published case studies

From technical signal to triage outcome

Technical reports state their evidence and limits. Process case studies document the disclosure outcome while withholding private report details.

Informative — Closed

Blind SSRF / DNS validation bypass

DNS-Resolved Private Address Bypass in a Server-Side JWKS Fetcher

A controlled callback and timing analysis showed that a hostname resolving to RFC1918 space reached a backend fetch stage, with impact limited to blind reconnaissance.

Severity
Medium
Testing
Authorized
Read the finding
Two reports — Duplicate (Closed)

Responsible disclosure process

Two Bug Bounty Reports, Two Duplicate Outcomes

A private-program reporting case study on evidence discipline, duplicate triage and the limits of what a public portfolio can claim.

Format
Process case study
Outcome
Duplicate
Read the case study

Independent methodology

Techniques to test and explain

These guides use fictional applications and synthetic data. They are educational examples, not claims of accepted vulnerabilities or program decisions.

Educational technique

Recovery-token exposure / browser telemetry

Tracing Password-Reset Secrets into Telemetry Requests

A synthetic workflow for checking whether a reset token in a page URL is copied into outbound telemetry, with controls that keep observation separate from account-takeover claims.

Format
Synthetic example
Read the technique
Educational technique

OAuth refresh-token replay assessment

Evaluating Refresh-Token Replay in a Public OAuth Client

A synthetic test plan for distinguishing a repeated refresh response from an independently usable token, with controls for client type, resource access and token binding.

Format
Synthetic example
Read the technique
Educational technique

Post-login open redirect

Validating Post-Login Redirects Without Overstating Impact

A synthetic method for checking whether a login continuation parameter sends an authenticated user to an external site, and for separating a real redirect from an unproven phishing scenario.

Format
Synthetic example
Read the technique

Publication standard

Technical detail with clear boundaries

Evidence over claims

Observed results are separated from hypothetical impact and synthetic teaching examples.

Disclosure status

Case studies follow their publication terms. Technique guides contain no live target, report ID, credential or private program detail.

Controlled validation

Practical checks focus on owned accounts, low request volumes and a reproducible final result.