Choosing the repository and fields for GitHub issues - Port Swigger
Summary: PortSwigger's documentation describes how Burp Suite DAST connections use actions to select the GitHub repository that receives issues and the fields the tool fills in, and users cannot raise GitHub issues through a connection until it has at least one action. Burp Suite DAST checks that GitHub accepts issues in the repository before saving an action, rejects archived repositories, repositories with issues turned off, and old names of renamed or moved repositories, and adds one severity label and one confidence label to every issue that cannot be turned off or renamed.
Key Takeaway: Issues raised in a public repository expose the details of each Burp Suite DAST issue to anyone who can read them, and if a repository is renamed or transferred in GitHub, the action silently stops raising issues until someone reselects it under its new name or owner.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026