High severityMulti-languageHardcoded SecretsHIGH confidence
Private Key Block
A PEM private-key block appears to be committed to source.
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
-----BEGIN RSA PRIVATE KEY-----Passes - the safe pattern
-----BEGIN CERTIFICATE-----Why it matters & how to fix it
A PEM private-key block appears to be committed to source. Remove the key, rotate the corresponding key pair/certificate, and store private keys in a secrets manager or hardware-backed keystore.
References
Rule ID integsec.generic.secrets.private-key-block - 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 - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials