config security issue: vault-root and vault-recovery keys are available as plaintext when using unseal feature in certain config #1660
Labels
area/security
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/keep
Denotes an issue or PR that should be preserved from going stale.
Describe the bug:
As an engineer, I want to make sure vault installation is secure.
when autounseal stanza is present, vault-root and vault-recovery keys are available as plaintext for any user that have access to s3 bucket. As well as for users without access to KMS.
Turns out, it is possible to configure both kmsid and s3sse options, which will lead to
vault-*
objects not encrypted.If I remove s3sse option from config,
vault-*
objects are uploaded encrypted.Expected behavior:
It is expected to vault-root, vault-recover-xx be encrypted KMS cipher texts when KMS key is specified. Or throw error when both kmsid and s3sse options are provided. I'm not sure what s3sse option supposed to do. I've expected it enables S3 sse.
Steps to reproduce the bug:
Create vault with awskms autounseal. Try to download vault-root from autounseal s3 bucket
Additional context:
Add any other context about the problem here.
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: