GHSA-vgh3-mwxq-rcp8 BIT-vault-2024-0831 CVE-2024-0831 GO-2024-2511
Hashicorp Vault may expose sensitive log information
- Severity
- 4.5 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.76%
- Chance of exploitation in the next 30 days. Higher than 55.43% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-532 Insertion of Sensitive Information into Log File
- Fix
1.15.5- Upgrade github.com/hashicorp/vault to this version or later
Description
Vault and Vault Enterprise (“Vault”) may expose sensitive information when enabling an audit device which specifies the log_raw option, which may log sensitive information to other audit devices, regardless of whether they are configured to use log_raw
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/hashicorp/vault | >= 1.15.0, < 1.15.5 |
1.15.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/hashicorp/vault Go → 1.15.5
- go
go get github.com/hashicorp/vault@v1.15.5 && go mod tidy
Severity breakdown
CVSS 3.1 4.5
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-532: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How to prevent it
- Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Distribution: Remove debug log files before deploying the application into production.
- Operation: Protect log files against unauthorized read/write.
- Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.
References
Advisories
Packages
Other links
- github.com/hashicorp/vault/commit/2a72f2a8a5b57de88c22a2a94c4a5f08c6f3770b
- developer.hashicorp.com/vault/docs/upgrading/upgrade-to-1.15.x
- discuss.hashicorp.com/t/hcsec-2024-01-vault-may-expose-sensitive-information-when-configur…
- security.netapp.com/advisory/ntap-20240223-0005
- security.netapp.com/advisory/ntap-20240223-0005
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-88v5-9hxc-f85r HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations | High | Also affects github.com/hashicorp/vault |
| GHSA-8r5m-3f66-qpr3 HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS | High | Also affects github.com/hashicorp/vault |
| GHSA-72gw-fmmr-c4r4 HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization | High | Also affects github.com/hashicorp/vault |
| GHSA-m2w4-8ggf-rj47 HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service | High | Also affects github.com/hashicorp/vault |
| GHSA-vp5w-xcfc-73wf Hashicorp Vault and Vault Enterprise vulnerable to a denial of service when processing JSON | High | Also affects github.com/hashicorp/vault |
| GHSA-9g4h-h484-3578 HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass | High | Also affects github.com/hashicorp/vault |
| GHSA-8f82-53h8-2p34 HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads | High | Also affects github.com/hashicorp/vault |
| GHSA-7rx2-769v-hrwf HashiCorp Vault ldap auth method may not have correctly enforced MFA | High | Also affects github.com/hashicorp/vault |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor