CVE intelligence and bounded remediation
CVE-2023-0690 — Hashicorp Boundary security vulnerability
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.
- Severity
- High
- CVSS
- 7.1 (3.1)
- Published
- 2023-02-08
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-312, CWE-311
Affected products
- hashicorp / boundary
Matched remediation archetype
Cryptography, certificate, signature, and channel validation
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
- Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
- Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.
Remediate safely
- Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
- Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
- Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.