Insecure Vibe Coding: When AI Writes Exploitable Software
summary
Three live demos show concrete failures and fixes: an expired JWT helper reused lets a signed token bypass authorization because verify_expiration=false is applied broadly; decoded input bypasses validation when URL-decoding happens after regex checks and the app concatenates into SQL, enabling injection; and SHA-256 allows 0.000042s crack vs Argon2 0.12s—fast hashing makes offline brute force trivial. Each demo ends with the specific change (separate refresh verifier, normalize-then-validate plus parameterized queries, use Argon2 with salts and work factor).
AI-written summary · about
chapters (11)
- 0:00Introduction and motivation
- 1:56What is vibe coding
- 5:06Confetti Club demo app
- 6:08JWT expiration bypass bug
- 13:14SQL injection via input decoding
- 20:23Password storage weakness
- 28:04Common structure of AI bugs
- 31:22Security review burden with AI
- 36:01Secure prompting checklist
- 40:14Integrating security into SSDLC
- 41:40Conclusion and Q&A
