HashiCorp Vault Unseal Key
ID |
hashicorp_vault_unseal_key |
Severity |
critical |
Vendor |
HashiCorp |
Family |
Other |
Description
HashiCorp provides open-source tools and commercial products that enable developers, operators and security professionals to provision, secure, run and connect cloud-computing infrastructure
HashiCorp Vault securely store and manage access to secrets and systems based on trusted sources of application and user identity. Secrets are stored in sealed logical vaults that need a master key to unseal. The master key needs a quorum (threshold) of unseal keys shares provided by different operators, following Shamir’s Secret Sharing algorithm.
This detector looks for hardcoded unseal keys used to get access to the vault master key.
Security
Any hardcoded HashiCorp Unseal Key is a potential secret reported by this detector.
Accidentally checking-in the key to source control repositories could compromise your HashiCorp Vault.
Mitigation / Fix
-
Remove the
Keyfrom the source code or committed configuration file. -
Follow your policy for handling leaked secrets, which typically require revoking the secret in the target system(s). Revoking the secret can be done by following the Documentation.
-
If under a git repository, you may remove unwanted files from the repository history using tools like
git filter-repoorBFG Repo-Cleaner. You may follow the procedure listed here for GitHub.
|
You should consider any sensitive data in commits with secrets as compromised. Remember that secrets may be removed from history in your projects, but not in other users' cloned or forked repositories. |