samber/cc-skills-golang / skills/golang-security
golang-security
FlaggedSecurity best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| evals/evals.json | config | 49.0 KB |
| references/architecture.md | markdown | 10.4 KB |
| references/checklist.md | markdown | 4.0 KB |
| references/cookies.md | markdown | 4.8 KB |
| references/cryptography.md | markdown | 11.0 KB |
| references/filesystem.md | markdown | 6.8 KB |
| references/injection.md | markdown | 7.3 KB |
| references/logging.md | markdown | 3.9 KB |
| references/memory-safety.md | markdown | 5.1 KB |
| references/network.md | markdown | 6.3 KB |
| references/secrets.md | markdown | 4.8 KB |
| references/third-party.md | markdown | 4.9 KB |
| references/threat-modeling.md | markdown | 8.4 KB |
references/cookies.md
View on GitHub# Cookie Security Rules
Cookie security is critical for preventing session hijacking and XSS exploitation.
**Rules:**
1. Cookies MUST set `HttpOnly` for session and authentication cookies.
2. Cookies MUST set `Secure` in production (HTTPS only).
3. `SameSite` SHOULD be `Lax` or `Strict` — use `None` only when cross-site access is required.
---
## Table of Contents
- [HTTP-Only Flag Missing — Medium](#http-only-flag-missing--medium)
- [Insecure Cookie Configuration (Missing Secure Flag) — Medium](#insecure-cookie-configuration-missing-secure-flag--medium)
- [SameSite Cookie Protection — Medium](#samesite-cookie-protection--medium)
- [Cookie Prefix Examples — Low](#cookie-prefix-examples--low)
- [Gorilla Sessions Cookie Security — High](#gorilla-sessions-cookie-security--high)
- [Cookie Best Practices Checklist](#cookie-best-practices-checklist)
- [CWE References](#cwe-references)
## HTTP-Only Flag Missing — Medium
Without HttpOnly flag, cookies can be accessed via JavaScript.
**Bad:**
```go
cookie := &http.Cookie{
Name: "session",
Value: sessionID,
// DON'T: Missing HttpOnly, Secure flags
}
```
**Good:**
```go
cookie := &http.Cookie{
Name: "session",
Value: sessionID,
HttpOnly: true, // Prevents JavaScript access
Secure: true, // Only sends over HTTPS
SameSite: http.SameSiteStrictMode,
Path: "/",
MaxAge: 3600,
}
```
---
## Insecure Cookie Configuration (Missing Secure Flag) — Medium
Without Secure flag, cookies are sent over unencrypted HTTP.
**Bad:**
```go
http.SetCookie(w, &http.Cookie{
Name: "auth_token",
Value: token,
// Missing Secure, HttpOnly flags
})
```
**Good:**
```go
http.SetCookie(w, &http.Cookie{
Name: "auth_token",
Value: token,
Secure: true, // HTTPS only
HttpOnly: true, // No JavaScript access
SameSite: http.SameSiteLaxMode,
Path: "/",
MaxAge: 86400,
Domain: "", // Default: send to exact host only
})
```
---
## SameSite Cookie Protection — Medium
SameSite attribute protects against CSRF attacks.
**Bad:**
```go
cookie := &http.Cookie{
Name: "session",
Value: token,
Secure: true,
HttpOnly: true,
// DON'T: Missing SameSite
}
```
**Good:**
```go
// Strict for high-security operations
authCookie := &http.Cookie{
Name: "auth",
Value: token,
Secure: true,
HttpOnly: true,
SameSite: http.SameSiteStrictMode,
}
// Lax for most applications
sessionCookie := &http.Cookie{
Name: "session",
Value: token,
Secure: true,
HttpOnly: true,
SameSite: http.SameSiteLaxMode,
}
// None for cross-site cookies (requires Secure: true)
crossSiteCookie := &http.Cookie{
Name: "analytics",
Value: trackingID,
Secure: true,
HttpOnly: true,
SameSite: http.SameSiteNoneMode,
}
```
---
## Cookie Prefix Examples — Low
Modern cookie prefixes enforce cookie behavior in browsers.
```go
// __Secure- prefix: Requires Secure flag
secureCookie := &http.Cookie{
Name: "__Secure-Session",
Value: token,
Secure: true, // Required for __Secure-
HttpOnly: true,
}
// __Host- prefix: Requires Secure, no Domain, origin-bound path
hostCookie := &http.Cookie{
Name: "__Host-CSRF",
Value: csrfToken,
Secure: true, // Required
HttpOnly: true,
Domain: "", // Must be empty
Path: "/", // Required
}
```
---
## Gorilla Sessions Cookie Security — High
**Bad:**
```go
import "github.com/gorilla/sessions"
store := sessions.NewCookieStore([]byte("secret-key")) // DON'T: Hardcoded key
```
**Good:**
```go
import "github.com/gorilla/sessions"
store := sessions.NewCookieStore(
[]byte(os.Getenv("SESSION_AUTH_KEY")), // Use env var
[]byte(os.Getenv("SESSION_ENC_KEY")), // Separate encryption key
)
store.Options = &sessions.Options{
Path: "/",
MaxAge: 86400 * 30,
HttpOnly: true,
Secure: true,
SameSite: http.SameSiteStrictMode,
}
```
---
## Cookie Best Practices Checklist
- [ ] Set `HttpOnly: true` for all authentication cookies
- [ ] Set `Secure: true` for all cookies over HTTPS
- [ ] Set appropriate `SameSite` value (Strict/Lax/None)
- [ ] Use short `MaxAge` expiration
- [ ] Avoid setting cookie `Domain` unless necessary
- [ ] Validate cookie values on every request
- [ ] Use cryptographically signed cookies
- [ ] Rotate cookie secrets regularly
- [ ] Clear cookies on logout
- [ ] Use double-submit cookie pattern for CSRF protection
---
## CWE References
- **CWE-1004**: Sensitive Cookie Without 'HttpOnly' Flag
- **CWE-614**: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
- **CWE-352**: Cross-Site Request Forgery (CSRF)
- **CWE-285**: Improper Authorization
- **CWE-565**: Reliance on Cookies without Validation
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |