High severityGoAuthentication & SecretsMEDIUM confidence
Hardcoded Credentials
A credential (password, API key, secret, or private key) appears to be hardcoded as a string literal (CWE-798).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)V2.10.4 (L2)
Vulnerable vs. safe
Flagged by this check
apiSecret := "aG9wZWZ1bGx5RmFrZVNlY3JldA=="Passes - the safe pattern
apiSecret := os.Getenv("API_SECRET")Why it matters & how to fix it
A credential (password, API key, secret, or private key) appears to be hardcoded as a string literal (CWE-798). Hardcoded secrets leak through source control, binaries, and backups, and cannot be rotated without a code change. Load secrets from environment variables or a secrets manager (Vault, AWS/GCP Secret Manager) at runtime, and rotate any value that was committed.
References
Rule ID integsec-go-hardcoded-credentials - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Authentication & SecretsHardcoded JWT Secret
- JavaScript / TypeScript - Authentication & SecretsHardcoded Secret
- JavaScript / TypeScript - Authentication & SecretsInsecure Cookie Flags
- JavaScript / TypeScript - Authentication & SecretsJWT Algorithm None
- JavaScript / TypeScript - Authentication & SecretsJWT Decode Without Verify
- JavaScript / TypeScript - Authentication & SecretsTLS Verification Disabled