First published: Wed Feb 08 2023(Updated: )
HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in the configuration file, new credentials created after an automatic rotation may not have been encrypted via the intended KMS. This would result in the credentials being stored in plaintext on the Boundary PKI worker’s disk. This issue is fixed in version 0.12.0.
Credit: security@hashicorp.com
Affected Software | Affected Version | How to fix |
---|---|---|
HashiCorp Boundary | >=0.10.0<0.12.0 |
Upgrade to Boundary 0.12.0. After upgrading, users should do one of the following to remediate the issue: * Wait for next worker authentication rotation to occur, typically within one week, at which point the new credentials should be properly encrypted. * Delete the worker from the system and re-authorize it, forcing the worker to generate a new set of credentials immediately, which will be encrypted.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2023-0690.
The severity of CVE-2023-0690 is high with a CVSS score of 7.1.
HashiCorp Boundary versions 0.10.0 through 0.11.2 are affected by CVE-2023-0690.
CVE-2023-0690 allows new credentials created after an automatic rotation to be not encrypted via the intended Key Management Service (KMS), resulting in the credentials being stored in plaintext.
Yes, upgrading HashiCorp Boundary to a version above 0.11.2 will fix the vulnerability.