dbcve.org
BoundaryApplication · Hashicorp

CVE-2023-0690

HIGH · 7.1 CVSS v3.1 Published 2023-02-08
Fix available
A fix is available. Upgrade to 0.12.0 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In HashiCorp Boundary versions 0.10.0-0.11.2, when a PKI-based worker is configured with a Key Management Service (KMS), credentials created after automatic rotation are not encrypted with the intended KMS, resulting in plaintext storage on disk.

MitigationUpgrade to Boundary version 0.12.0 or later to remediate. Additionally, audit the PKI worker disk for any plaintext credentials that may have been stored during the affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BoundaryApplication
Affected:>= 0.10.0, < 0.12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Boundary version
    Run `boundary --version` or check the binary version used in your deployment
    Affected if Version is 0.10.0 through 0.11.2 (any version >= 0.10.0 and < 0.12.0)
  2. Confirm PKI worker configuration
    Review Boundary controller/worker configuration files for `worker` type set to `pki` or check worker registration status via `boundary workers list -scope id=global`
    Affected if PKI-based workers are configured and registered in the environment
  3. Verify KMS is configured for workers
    Inspect Boundary configuration for `kms` blocks, particularly those intended for worker storage encryption or review output of `boundary kms list`
    Affected if A Key Management Service (KMS) is configured for use with workers
  4. Inspect worker storage for plaintext credentials
    Examine the storage location where worker credentials are persisted (typically the worker data directory or configured storage backend) for any unencrypted credential files created after rotation events
    Affected if Plaintext credential files exist in worker storage locations

You are affected if running Boundary 0.10.0-0.11.2 with PKI workers that have KMS configured, and unencrypted credentials exist on disk after automatic rotation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.12.0 or later
Fixed in 0.12.0
Interim mitigation

Upgrade to Boundary version 0.12.0 or later to remediate. Additionally, audit the PKI worker disk for any plaintext credentials that may have been stored during the affected versions.

Recommended fix High confidence

0.12.0

  1. 1. Review the HashiCorp Boundary upgrade documentation for your deployment type
  2. 2. Create a backup of your current Boundary configuration and database
  3. 3. Plan your upgrade path: upgrade first any workers, then the controllers, following HashiCorp's recommended sequence
  4. 4. Upgrade Boundary to version 0.12.0 or later
  5. 5. Verify that the KMS configuration is properly loaded and functioning after upgrade
  6. 6. Confirm that newly rotated credentials are now encrypted via the intended KMS by checking worker logs and storage
Caveat Review the 0.12.0 release notes for any configuration or behavioral changes before upgrading, as minor version upgrades may include breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Boundary Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0690 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data