title: Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured
description: 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.
problem types: CWE-312 Cleartext Storage of Sensitive Information
affected:
{
vendor: HashiCorp
product: Boundary
platforms: [Windows, MacOS, x86, ARM, 64 bit, Linux, 32 bit]
repo: https://github.com/hashicorp/boundary
versions:
status: affected, version: 0.10.0, lessThanOrEqual: 0.11.2, versionType: semver
defaultStatus: unaffected
}
metrics:
format: CVSS
scenarios: GENERAL
cvssV3_1: [
version: 3.1
attackVector: LOCAL
attackComplexity: HIGH
privilegesRequired: HIGH
userInteraction: REQUIRED
scope: CHANGED
confidentialityImpact: HIGH
integrityImpact: NONE
availabilityImpact: NONE
baseSeverity: MEDIUM
baseScore: 5
vectorString: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N
]
solutions: 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.