golang-security

To prevent SQL injection and command injection in Go, use parameterized SQL queries and execute commands via exec.Command without shell interpolation. This skill provides concrete defense-in-depth patterns for validating inputs and securing I/O operations against malicious code execution.

Performing a Go security audit involves using a trust-boundary-first approach with STRIDE threat modeling and DREAD-based severity prioritization. This skill guides you through reviewing injection risks, unsafe cryptography, path traversal, and insecure cookies to identify high-impact flaws.

The best way to secure file paths and prevent ZipSlip in Go is by enforcing safe path confinement using os.Root and implementing zip bomb limits. This skill provides specific filesystem safety patterns to restrict directory traversal and handle untrusted archives securely.

Yes, you can use govulncheck for verified dependency scanning during a Go security review. This skill recommends operational verification guidance including govulncheck, security linters, and go test -race to detect vulnerable packages and concurrency issues before production deployment.

Html/template auto-escaping prevents XSS vulnerabilities in Go by contextually sanitizing dynamic data before rendering HTML output. This skill outlines vulnerability prevention patterns for injection risks including XSS, ensuring external user input is safely handled across templates.

To avoid nonce safety issues with AES-GCM in Go, enforce strict cryptographic rules ensuring nonces are never reused with the same key and TLS configurations meet modern security standards. This skill provides safe cryptography usage patterns to prevent high-impact security flaws.