LLMs can now reliably spot real-world zero-day vulnerabilities through brute-force patience – this deep-dive explains why that's both impressive and a...
LLMs can now reliably spot real-world zero-day vulnerabilities through brute-force patience – this deep-dive explains why that's both impressive and alarming.
The candidate applied for an open backend position at our company Vidoc Security Lab. He had a decent CV and LinkedIn profile but used a deepfake during the coding interview, pretending to be a different person. This incident could be linked to a North Korean hacker group that has used this trick with many other companies.
Part II of the Developer's Guide for a secure API implementation. Devs are the core of web applications, that's why you should continue learning how to prevent common attacks and secure your endpoints correctly. Avoid deploying vulnerable code by taking into account these Security Best Practices.
Explore the technical essentials of Software Composition Analysis (SCA) and dependency scanning, crucial tools for securing software against cyber threats in AI-driven development environments.
The perfect introduction for those wanting to understand Prototype Pollution vulnerabilities and exploits. Because not everyone knows how Objects in JavaScript work, but we are about to change that! Are you up for the challenge?
Beginners guide to this common security misconfiguration. Here you'll find the steps to quickly spot and exploit CORS vulnerabilities out in the wild. Shall we start?
SAST tools overlook more than 85% of CVEs in real-world scenarios. Outdated security automation can't keep pace with rapid code development. There is the hidden cost of security automation - validating false positives.
Discover how to safeguard your applications with effective secrets management. Learn about the challenges of secrets detection and how Vidoc Security Lab's AI Security Engineer can revolutionize your security measures against AI-generated code threats.
Developer's Guide for a secure API implementation. Devs are the core of web applications, however, they are also the ones who end up introducing and deploying vulnerabilities that later get exploited. That's why you should know how to prevent common attacks and secure your endpoints correctly.
Distinguishing between SAST & DAST is crucial for any robust security strategy. Adopting a unified approach, by leveraging both scans, ensures that your software remains secure during its lifecycle, effectively mitigating potential risks and vulnerabilities in today's fast-paced digital environment.
In the rapidly evolving cybersecurity landscape, where the emergence of AI-generated code presents unprecedented challenges, the concept of automated penetration testing emerges as a beacon of innovation and efficiency.
Beginners guide to Reflected XSS. Everyone talks about the different XSS cheatsheets, and then you are supposed to try them one by one to see if any of the payloads get executed on your target. We don't like that. It's time-consuming and a mindless task.
The impact of an AWS S3 Bucket Takeover can range from none, account takeover, and even up to RCE. In this article, we'll tell you how to find it and maximize its impact
Next.js 14 (and 13) introduced many attack vectors without providing the tooling necessary for organizations to detect them. It is easier than ever before to expose server secrets, introduce unauthenticated "endpoints" or any other issue that will make you vulnerable
Security implications of DEBUG=true in Django. Learnings from an ethical hacker's perspective
Vidoc Security Lab has secured an investment from bValue, a leading player in the world of venture capital and technology innovation
We implemented Notification and Collaboration features. How it works and how it can benefit your research
As a security researcher, I absolutely love the rush of discovering a suspicious endpoint during reconnaissance (which is super easy with Vidoc Research tool ;). It's exciting to think that you might have stumbled upon something important. However, that excitement can quickly turn into frustration when you're met with a 401 or 403 HTTP response code. Trust me, I've been there. But, over time, I've learned that there are ways to work around these error codes. I want to share some practical tips and techniques that I learned doing research, along with links to modules you can run in Vidoc Research to try to bypass 401 and 403.
2022 was very busy for several reasons, today we want to present to you what we did and learned doing large-scale bug bounty hunting
TL;DR; We improved Active Recon and data search option, changed payments system to subscription model, introduced Module-based security scanning with nuclei-like templates, and introduced Module Editor.
What sucks the most about doing recon? It all started with that one tweet ;) Inspired by Greg's post we decided to write a summary of common problems with Recon and why Vidoc Research - our tool for security researchers - solves them all.
TL;DR Vidoc platform will allow you to find new targets, test your payloads and collaborate with other professionals. The application security recon tool and scanner we are working on is dedicated to modern web applications. Our goal is to make big scale research affordable and easy for everybody.
We have reported more than 60 instances of this bug across a wide range of bug bounty programs including companies like Paypal, Atlassian, Microsoft, GitLab, Yahoo, ...
