Zoom Security Exploit: Cracking private meeting passwords
I believe Zoom&#x27;s continued struggle represents the state of software development in 2020.<p>1. Are you a software engineer?<p>2. How many &quot;security&quot; tickets have you been assigned in your career?<p>3. Has your employer ever paid for security training for you? (and I&#x27;m not talking about annoying powerpoint websites that teach you how to identify phishing emails)<p>4. Has your organization ever run a blue team &#x2F; red team exercise?<p>5. Who is in charge of APPLICATION SECURITY at your company? (Not network security, or database security, but actual APPLICATION level vulns)<p>6. Does your organization scan for outdated dependencies? (Do you uncover CVEs in your software on your own, or do you check how bad things are when the news tells you something big happened and might be in your stack?)<p>7. Are you running a web application, and have you implemented ANY security headers?<p>8. Did your business unit mandate that &quot;we support all browsers&quot;, so they still have you running on TLS v1.1? (who tf knows, or cares, am I right?)<p>9. Do you use the software you built? (Is your personal information in the database, along with legitimate usage stats, and possibly sensitive information you&#x27;d like to protect, or do you just write the code and deploy into the void?)<p>10. Do you have access to the production systems or database? (Most likely the answer is NO, so you wouldn&#x27;t know about brute-force attacks, invalid requests, corrupted data, or other anomalies the developers should have their eyes on).<p>My diagnosis; the profession of software development is a victim of a hostile takeover from product managers, while pushing engineers out of control of their domain.<p>My recommendation; use the least amount of software you can get by with, and assume it&#x27;s compromised.