Attack PathsMeridian Mutual
◆ Reasoning engine · CHAIN-01
Public internet → every customer's claims data
A single proven kill chain — each hop backed by a gate-verified finding you can open and replay.
Entry
Unauthenticated
Public surface, no credentials
initial access
→
Hop 1 · foothold
High
Forgotten staging console yields a portal session
GT-2044
● proven
→
Hop 2 · recon
Medium
Error leak maps internal API host
GT-2052 · mdb-primary.internal
● proven
→
Hop 3 · exploit
Critical
Cross-tenant IDOR reads every tenant's documents
GT-2041
● proven · TIER 4
→
Impact
Business impact
Every customer's policy & claims data
data exposure
Why the chain matters
In isolation these are a high, a medium, and a critical. Chained, an attacker starts unauthenticated, obtains a session through the exposed staging console, then abuses the cross-tenant flaw to read every customer's policy and claims documents. The critical link was only reachable behind the login — a public-surface scan stops at the console.
Hops: 3
Every hop: gate-verified
Fix GT-2041 → chain broken