Stranger Danger: Tracking Vulnerabilities in Your Third Party Code
summary
A live demo runs Snyk Stranger against a Node app (npm ~200,000 packages, 2.5B monthly downloads) and immediately reports five vulnerabilities; one outdated transitive dependency is exploitable and a prepared payload yields a reverse shell exploit on the demo machine. The tool offers guided upgrades, downstream patching from an open patch database, CI/test integration and dependency snapshots; research cited shows ~11% npm packages with known vulns and repair times measured in hundreds of days.
AI-written summary · about
chapters (7)
- 0:00Open source benefits
- 0:22Security risks in open source
- 1:26Third-party dependency risks
- 3:49Introducing the Snyk tool
- 5:08Live exploit demonstration
- 8:23Fixing vulnerabilities
- 11:00Best practices and conclusion
related talks
24mStrangerDanger: Finding Security Vulnerabilities Before They Find You!
27mStrangerDanger: Finding Security Vulnerabilities Before They Find You
35mStrangerDanger: Finding Security Vulnerabilities Before They Find You!
34mStranger Danger: Finding Security Vulnerabilities Before They Find You!
10mGuy Podjarny, Snyk | Node Summit 2017
40mSecuring your dependencies
37mStranger Danger: Finding Security Vulnerabilities Before They Find You!
47mBlack Clouds and Silver Linings in Node.js Security
