Security Resilience

CVE-2023-0690

Hashicorp Boundary 0.10.0 – 0.12.0

Published
08 February 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N
EPSS Score 0.0044 36th percentile
Risk Priority 37 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-0690 is a medium-severity Cleartext Storage of Sensitive Information (CWE-312) vulnerability in Hashicorp Boundary. Its CVSS base score is 5.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1016.001 Internet Connection Discovery Discovery
Adversaries may check for Internet connectivity on compromised systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-1052Same product: Hashicorp Boundary
CVE-2024-12289Same product: Hashicorp Boundary
CVE-2023-41096Shared CWE-311, CWE-312
CVE-2023-41095Shared CWE-311, CWE-312
CVE-2023-30523Shared CWE-311, CWE-312
CVE-2023-32982Shared CWE-311, CWE-312
CVE-2024-6104Same vendor: Hashicorp
CVE-2024-2877Same vendor: Hashicorp
CVE-2024-8365Same vendor: Hashicorp
CVE-2025-1296Same vendor: Hashicorp

Affected Assets

hashicorp
boundary
0.10.0 — 0.12.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V14.2.8

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-311 CWE-312

Privacy and security training stresses encryption of sensitive data, reducing missing encryption weaknesses.

addresses: CWE-311 CWE-312

The map highlights data actions that involve sensitive data, enabling identification of missing encryption requirements.

addresses: CWE-311 CWE-312

Settings can require encryption of sensitive data, preventing missing encryption weaknesses.

addresses: CWE-311

Exchange agreements must document security requirements, which would include encryption to protect sensitive data in transit.

addresses: CWE-312

Policy requires protection measures such as encryption for sensitive data stored on media, preventing cleartext exposure.

addresses: CWE-311

Architectures must describe confidentiality protections, which includes mandating encryption for sensitive data in transit and at rest.

addresses: CWE-311

Privacy and security curricula stress encryption requirements, reducing missing encryption of sensitive data.

addresses: CWE-311

Requires encryption and similar controls for CUI processed or stored externally, preventing missing encryption of sensitive data.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 partial match
blocks

Encryption and cryptographic controls for data-at-rest directly prevent cleartext storage of sensitive information.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Explicit rules requiring encryption for sensitive information in transit eliminate the weakness of sending data without cryptographic protection.

finds

When clear-text sensitive data is detected leaving controlled storage, the control can block the transfer, thereby limiting the exposure that would result from unencrypted storage on external media or cloud services.

removes

created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).

blocks

Explicitly calling for protection of data in transit and at rest, plus secure encryption of communications, drives the implementation of encryption that prevents clear-text exposure of sensitive information.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248525 All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. blocks CWE-312
Oracle Linux 9 (1 rule)
  • V-271756 OL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312
RHEL 8 (1 rule)
  • V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312

References