Pull requests are a core part of collaboration, whether in open or closed source. GitHub has documented some of the security consequences of misconfiguring how PRs can trigger actions. But what happens when repo owners don't read the docs? Bar Kaduri and Roi Nisimi walk through their experience in reading docs, finding vulns, demonstrating exploits, and working with repo owners to improve their security. Their work highlights the challenges in maintaining good security guidance, figuring out secure defaults, and how so many orgs still struggle with triaging external security reports -- something that's becoming even more challenging when orgs are being flooded with low-quality reports from LLMs. Segment Resources: <ul> <li><a rel="noopener" target="_blank" href= "https://orca.security/resources/blog/pull-request-nightmare-github-actions-rce/"> https://orca.security/resources/blog/pull-request-nightmare-github-actions-rce/</a></li> <li><a rel="noopener" target="_blank" href= "https://orca.security/resources/blog/pull-request-nightmare-part-2-exploits/"> https://orca.security/resources/blog/pull-request-nightmare-part-2-exploits/</a></li> </ul> Visit <a rel="noopener" target="_blank" href= "https://www.securityweekly.com/asw">https://www.securityweekly.com/asw</a> for all the latest episodes! Show Notes: <a rel="noopener" target="_blank" href= "https://securityweekly.com/asw-355">https://securityweekly.com/asw-355</a>

Podurama

Home

Trending

Personal

Your Podcasts

New Episodes

My Files

Favourite Episodes

Tags (Folders)

Recently Played

Bookmarks

Followed Playlists

Researching and Remediating RCEs via GitHub Actions - Bar Kaduri, Roi Nisimi - ASW #355

Application Security Weekly (Audio)

AI Chapters

AI Insights

Reviews