Affected by GO-2022-0611
and 21 other vulnerabilities
GO-2022-0611: HashiCorp Vault Incorrect Permission Assignment for Critical Resource in github.com/hashicorp/vault
GO-2022-0618: Hashicorp Vault Privilege Escalation Vulnerability in github.com/hashicorp/vault
GO-2022-0623: Invalid session token expiration in github.com/hashicorp/vault
GO-2022-0632: Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault in github.com/hashicorp/vault
GO-2022-0816: Improper Resource Shutdown or Release in HashiCorp Vault in github.com/hashicorp/vault
GO-2022-0825: Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault in github.com/hashicorp/vault
GO-2023-1685: HashiCorp Vault’s Microsoft SQL Database Storage Backend Vulnerable to SQL Injection Via Configuration File in github.com/hashicorp/vault
GO-2023-1708: HashiCorp Vault's PKI mount vulnerable to denial of service in github.com/hashicorp/vault
GO-2023-1849: Hashicorp Vault vulnerable to Cross-site Scripting in github.com/hashicorp/vault
GO-2023-1897: HashiCorp Vault's revocation list not respected in github.com/hashicorp/vault
GO-2023-1900: Hashicorp Vault Fails to Verify if Approle SecretID Belongs to Role During a Destroy Operation in github.com/hashicorp/vault
GO-2023-1986: HashiCorp Vault and Vault Enterprise vulnerable to user enumeration in github.com/hashicorp/vault
GO-2023-2088: Hashicorp Vault Incorrect Permission Assignment for Critical Resource vulnerability in github.com/hashicorp/vault
GO-2023-2329: HashiCorp Vault Missing Release of Memory after Effective Lifetime vulnerability in github.com/hashicorp/vault
GO-2024-2485: HashiCorp Vault Improper Privilege Management in github.com/hashicorp/vault
GO-2024-2486: HashiCorp Vault Improper Privilege Management in github.com/hashicorp/vault
GO-2024-2488: HashiCorp Vault Authentication bypass in github.com/hashicorp/vault
GO-2024-2514: Token leases could outlive their TTL in HashiCorp Vault in github.com/hashicorp/vault
GO-2024-2617: Authentication bypass in github.com/hashicorp/vault
GO-2024-2690: HashiCorpVault does not correctly validate OCSP responses in github.com/hashicorp/vault
GO-2024-2921: HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims in github.com/hashicorp/vault
GO-2024-3191: Vault Community Edition privilege escalation vulnerability in github.com/hashicorp/vault
type Config struct {
// Location is the path in the storage backend for the// salt. Uses DefaultLocation if not specified.
Location string// HashFunc is the hashing function to use for salting.// Defaults to SHA1 if not provided.
HashFunc HashFunc// HMAC allows specification of a hash function to use for// the HMAC helpers
HMAC func() hash.Hash// String prepended to HMAC strings for identification.// Required if using HMAC
HMACType string
}
type Salt struct {
// contains filtered or unexported fields
}
Salt is used to manage a persistent salt key which is used to
hash values. This allows keys to be generated and recovered
using the global salt. Primarily, this allows paths in the storage
backend to be obfuscated if they may contain sensitive information.