Add OopsSec Store to Apps section - #566
Open
kOaDT wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds OopsSec Store to the Apps section.
What it is
An intentionally vulnerable e-commerce application built on the Next.js App Router, React, TypeScript and Prisma. It ships 36 CTF challenges across 11 chapters, each with a walkthrough that goes from vulnerability to exploit to fix.
Why it belongs on this list
It is a Next.js learning resource first, a security lab second. Most vulnerable-app projects target older stacks (Juice Shop on Express/Angular, DVWA on PHP), so the lessons do not transfer to how Next.js developers actually ship code. This one puts the vulnerability classes where Next.js developers meet them:
NEXT_PUBLIC_secrets leaking into the client bundleThe point is that a Next.js developer walks away knowing how to secure their own app, not just how to break someone else's.
Details
npx create-oss-store my-ctf-labordocker run -p 127.0.0.1:3000:3000 leogra/oss-oopssec-storeThe app is designed to be run locally in an isolated environment and carries explicit warnings against production deployment.
Checklist
[Title Case Name](link) - Description.