
OWASP Top 10 Part 8: Software or Data Integrity Failures | Ep 204
Part 8 of our OWASP Top 10 series covers Software or Data Integrity Failures, the category Brad thinks would jump to number one if OWASP released a list today. Brad and Jordan explain why it covers much more than vulnerable libraries: it applies to any third-party resource your application trusts without checking it, whether that’s code, firmware, a domain or user input.
They get into how AI-assisted “vibe coding” has quietly pushed this risk into almost every organization and its vendors. Brad tells the story of an AI assistant that pulled in a compromised GitHub fork and poisoned his whole project. He also walks through two recent client incidents: a legacy package that resurfaced on a production server, and card-skimming JavaScript buried in a vendor’s tracking library.
In this episode:
- Why “trust” is the common thread across this whole category
- Cookie scoping and the risk of trusting parent domains and subdomains
- How AI coding tools pick dependencies, and why your vendors’ vibe coding affects you too
- Unsigned firmware updates in medical and industrial devices
- Getting libraries from official sources, not lookalike repos
- Insecure deserialization, explained as a letter in an envelope
- Mass assignment and the “isAdmin=true” privilege escalation
- Pinning libraries and images in CI/CD pipelines
D'autres épisodes de "The Cyber Threat Perspective"



Ne ratez aucun épisode de “The Cyber Threat Perspective” et abonnez-vous gratuitement à ce podcast dans l'application GetPodcast.








