Affected by GO-2022-0611
and 22 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-0778: Information Disclosure 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
Package template is responsible for rendering user supplied templates to
disk. The Server type accepts configuration to communicate to a Vault server
and a Vault token for authentication. Internally, the Server creates a Consul
Template Runner which manages reading secrets from Vault and rendering
templates to disk at configured locations
type Server struct {
// Templates holds the parsed Consul Templates Templates []*ctconfig.TemplateConfig DoneCh chan struct{}
// contains filtered or unexported fields
}
Server manages the Consul Template Runner which renders templates
Run kicks off the internal Consul Template runner, and listens for changes to
the token from the AuthHandler. If Done() is called on the context, shut down
the Runner and return
type ServerConfig struct {
Logger hclog.Logger
// Client *api.Client VaultConf *config.Vault ExitAfterAuth bool Namespace string// LogLevel is needed to set the internal Consul Template Runner's log level// to match the log level of Vault Agent. The internal Runner creates it's own// logger and can't be set externally or copied from the Template Server.//// LogWriter is needed to initialize Consul Template's internal logger to use// the same io.Writer that Vault Agent itself is using. LogLevel hclog.Level
LogWriter io.Writer}
ServerConfig is a config struct for setting up the basic parts of the
Server