HashiCorp Boundary up to 0.11.2 Key Management Service cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HashiCorp Boundary up to 0.11.2. It has been classified as problematic. This impacts an unknown function of the component Key Management Service. Performing a manipulation results in cleartext storage. This vulnerability is cataloged as CVE-2023-0690. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in HashiCorp Boundary up to 0.11.2. This affects an unknown code block of the component Key Management Service. The manipulation with an unknown input leads to a cleartext storage vulnerability. CWE is classifying the issue as CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was shared 02/08/2023. The advisory is shared at discuss.hashicorp.com. This vulnerability is uniquely identified as CVE-2023-0690 since 02/06/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
Upgrading to version 0.12.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.7
VulDB Base Score: 1.9
VulDB Temp Score: 1.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
CNA Base Score: 5.0
CNA Vector (HashiCorp Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Boundary 0.12.0
Timeline
02/06/2023 🔍02/08/2023 🔍
02/08/2023 🔍
03/09/2023 🔍
Sources
Advisory: discuss.hashicorp.comStatus: Confirmed
CVE: CVE-2023-0690 (🔍)
GCVE (CVE): GCVE-0-2023-0690
GCVE (VulDB): GCVE-100-220449
Entry
Created: 02/08/2023 21:09Updated: 03/09/2023 06:56
Changes: 02/08/2023 21:09 (50), 03/09/2023 06:56 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.