Repository navigation
Showcase: outside-in "leak check" of a production Next.js + Stripe app on Windows #1406
gold567200
started this conversation in
Show and tell
Replies: 1 comment
|
سلام عليكم |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Target: Our own production client portal (Next.js 16 / Turbopack, Postgres, Stripe, behind a Cloudflare Tunnel), checked from the outside with no code access first, then cross-checked against source.
Question: What can an attacker see and reach without logging in? Specifically: secrets or source in the shipped JavaScript, hidden endpoints, auth bypasses, and transport and header gaps.
How REA helped:
list-browser-targets+inspect-web-pageagainst an isolated headless Chrome (own temp profile, loopback CDP) gave evidence-backed answers to "what does this page load and store": 15 scripts, none declaring a source map, and zero localStorage, sessionStorage or IndexedDB keys, so there are no tokens for an injected script to steal. The evidence IDs went straight into the client-style report.What we found:
.mapURLs 404.x-middleware-subrequestbypass didn't work.Securesession cookie and HSTS limited the impact. Fixed with Cloudflare's Always Use HTTPS.Rough edge, for the maintainers:
analyze-javascript-applicationon the downloaded Turbopack chunk directory (15 files, ~700 KB) ran 20+ minutes at ~3.5 GB RSS without finishing (6.3.0, Windows, Node 24.21). Happy to share more detail if useful.We now offer this as a fixed-price service for small businesses and indie apps: https://goldenrockadvancements.com/audit/
All reactions