LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0690: Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured

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.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

HashiCorp Boundary workers could store rotated credentials in plaintext on disk even when KMS encryption was configured. The business risk is credential disclosure if someone can access the affected worker disk. The vendor says the issue is fixed in Boundary 0.12.0.

Executive priority

Prioritize remediation for Boundary deployments protecting sensitive access paths. This is not documented as internet-exploited, but plaintext credentials can turn local disk access into broader access exposure.

Technical view

CVE-2023-0690 affects HashiCorp Boundary 0.10.0 through 0.11.2 using PKI-based workers with KMS defined. After automatic credential rotation, new credentials may not be encrypted by the intended KMS and may be written plaintext to worker disk. The CVSS 3.1 score is 5.0, with high confidentiality impact.

Likely exposure

Exposure appears limited to Boundary deployments running affected versions with PKI-based workers, KMS configuration, and automatic credential rotation. Practical risk depends on whether rotations occurred and who can access worker disks or backups.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. The CVSS vector indicates local access, high privileges, high attack complexity, and user interaction, so this is mainly a credential exposure risk after host or disk access.

Researcher notes

Evidence is narrow but clear: the issue concerns rotated credentials on PKI workers when KMS is configured. Sources do not provide public exploit details, affected CPEs, or mitigation beyond the fixed version, so validation should focus on configuration and rotation history.

Mitigation direction

  • Upgrade HashiCorp Boundary to version 0.12.0 or later.
  • Review HashiCorp HCSEC-2023-03 for deployment-specific guidance.
  • Treat exposed worker-disk credentials as potentially compromised.
  • Rotate any credentials that may have been stored plaintext.
  • Restrict and audit access to Boundary worker disks and backups.

Validation and detection

  • Inventory Boundary versions across controllers and workers.
  • Identify PKI-based workers with KMS configured.
  • Confirm whether automatic credential rotation occurred on affected versions.
  • Review worker disk storage for plaintext rotated credentials.
  • Verify upgraded workers no longer create plaintext credentials after rotation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-312: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-0690 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N0.64Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2023-0690Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HashiCorpBoundary0.10.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-312 · source CWE mapping

Cleartext Storage of Sensitive Information

Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.