Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| HashiCorp | Boundary | unaffected |
|
No data.
No data available yet.
Vendor Solution
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.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2019 | 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. |
Github GHSA |
GHSA-9vrm-v9xv-x3xr | HashiCorp Boundary Workers Store Rotated Credentials in Plaintext Even When Key Management Service Configured |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.437% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|