SecureLayer7

Introducing Sandyaa: An Open-Source Autonomous Code Auditor blog.securelayer7.net/sandyaa-open-s…

Open-sourced Sandyaa - autonomous source code auditor and finding zeroday is fun!! Point it at any repo, get runnable PoCs with evidence chains back to file. No API key piggybacks on your Claude Code CLI. github.com/securelayer7/s…

We are going to discuss with Security Leader Shobit and @cure53berlin about the these issue: us06web.zoom.us/webinar/regist…

As a pentest engagement leader, how do you usually react when you get a bloated, noisy pentest report?

Here are the TOP misreported findings you should never accept in a pentest report. With us @cure53berlin, @SandeepL337, and Shobhit Mehta — let’s unpack such vulnerability which is not real. Join this interesting firechat: us06web.zoom.us/webinar/regist…

Join cybersecurity leaders for a fireside chat on spotting false positives in pentest reports, prioritizing real risks, and improving remediation workflows. Who Should Attend: CISOs, Security leaders, pentesters, and security teams. Register here - us06web.zoom.us/webinar/regist…

CVE-2025-25364: Speedify VPN MacOS privilege Escalation blog.securelayer7.net/cve-2025-25364…

Windows Telephony Services: 2025 Patch Diffing & Analysis blog.securelayer7.net/windows-teleph…

We will continue expanding this list based on our experiences at SL7 and contributions from others until January 31, 2025, after which the list will be finalized. Feel free to submit pull requests!

Updated: Top 2025 vulnerabilities you shouldn’t accept in a pentest report [DRAFT] Introducing three different sections: 1. Minor Infrastructure Information Exposure 2. Reporting Unexploitable Vulnerabilities 3. Problems Without Security-Related Impact github.com/securelayer7/n…

We’d love to hear additional contexts that don’t make sense in pentest report. Submit your pull requests or issues. We aim to finalize this draft by the 31st for practitioners and pentesters. github.com/securelayer7/n…

We extend our heartfelt gratitude to SecureLayer7 for being a Gold Sponsor of the Seasides Conference! Your invaluable support plays a vital role in fostering knowledge-sharing within the security community. Thank you, SecureLayer7 Sandeep Kamble , for championing this mission

@0xTib3rius Valid point - context is critical. and updated with this details Some browsers (Chrome) delay or throttle background requests in inactive tabs meaning keep-alive signals might not be sent on time. This could lead the session to persist longer than expected even with a timeout set

Some of these are good. Some are questionable. There's a lot that really require context. For example, saying that long session timeouts "isn't a vulnerability; it's a design decision". Well, it *can* be a design decision. What if it's not? What if the developer used a bad default value? Pentesters shouldn't make assumptions about these things. Customers are perfectly capable of accepting the risk of findings in a report.

Metasploitable3 takes pentesting to the next level with new vulnerabilities and challenges. blog.securelayer7.net/metasploitable…

The list is designed to be educational. We’ll update each point with detailed explanations of why it doesn’t matter and provide the context to support it.

Top 2025 vulnerabilities you shouldn’t accept in a pentest report. Here is list! Looking for more such scenarios. github.com/securelayer7/n…

@albinowax You make a valid point! While a strict CSP can significantly reduce the risk of XSS, it isn't a foolproof solution. Especially with creative exploitation techniques like JSONP abuse, improperly sanitized data in inline event handlers, or compromised third-party scripts. REMOVED.

I have to disagree with this post's claim that you shouldn't report or patch "XSS vulnerabilities mitigated by strict CSP". Strict CSP configurations can get bypassed and HTML injection & style injection are both threats too! CSP is for defence in depth.