Affected by GO-2022-0618
and 16 other vulnerabilities
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-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-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-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-3191: Vault Community Edition privilege escalation vulnerability in github.com/hashicorp/vault
func DecodeJSON(data []byte, out interface{}) error
DecodeJSON tries to decompress the given data. The call to decompress, fails
if the content was not compressed in the first place, which is identified by
a canary byte before the compressed data. If the data is not compressed, it
is JSON decoded directly. Otherwise the decompressed data will be JSON
decoded.
EncodeJSONAndCompress encodes the given input into JSON and compresses the
encoded value (using Gzip format BestCompression level, by default). A
canary byte is placed at the beginning of the returned bytes for the logic
in decompression method to identify compressed input.
Affected by 
Documentation
¶
Source Files