Contributors

Vulnerability Credits

Sort ↑

9 matches for “CodeQL”.

#Name or organizationAdvisories
1 <a href="https://www.linkedin.com/in/benjaminrodes">Benjamin Rodes</a> with Microsoft CodeQL2
2 <a href="https://twitter.com/20brokensp">Sam Pope</a> with MSRC Vulnerabilities &amp; Mitigations and Benjamin Rodes with Microsoft CodeQL1
3 CodeQL1
4 CodeQL team members [@atorralba (Tony Torralba)](https://github.com/atorralba) and [@joefarebrother (Joseph Farebrother)](https://github.com/joefarebrother).1
5 Discovered via CodeQL automated scanning on GitHub1
6 This incomplete fix was discovered and reported by the CodeQL team member [@atorralba (Tony Torralba)](https://github.com/atorralba) and [@jarlob (Jaroslav Lobačevski)](https://github.com/jarlob) from Github Security Lab. The new ReDos was discovered by the Apache Tika team.1
7 This issue was discovered and reported by the CodeQL team members [@atorralba (Tony Torralba)](https://github.com/atorralba) and [@joefarebrother (Joseph Farebrother)](https://github.com/joefarebrother).1
8 This issue was discovered by GitHub's CodeQL code scanning service.1
9 Tony Torralba and Joseph Farebrother from the GitHub CodeQL team.1