fix(deps): update module github.com/hashicorp/vault to v1.14.8 [security] #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.14.1
->v1.14.8
GitHub Vulnerability Alerts
CVE-2023-4680
HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphertext and potentially derive the authentication subkey when using transit secrets engine without convergent encryption. Introduced in 1.6.0 and fixed in 1.14.3, 1.13.7, and 1.12.11.
CVE-2023-5954
HashiCorp Vault and Vault Enterprise inbound client requests triggering a policy check can lead to an unbounded consumption of memory. A large number of these requests may lead to denial-of-service. Fixed in Vault 1.15.2, 1.14.6, and 1.13.10.
CVE-2023-6337
HashiCorp Vault and Vault Enterprise 1.12.0 and newer are vulnerable to a denial of service through memory exhaustion of the host when handling large unauthenticated and authenticated HTTP requests from a client. Vault will attempt to map the request to memory, resulting in the exhaustion of available memory on the host, which may cause Vault to crash.
Fixed in Vault 1.15.4, 1.14.8, 1.13.12.
Release Notes
hashicorp/vault (github.com/hashicorp/vault)
v1.14.8
Compare Source
1.14.8
SECURITY:
CHANGES:
BUG FIXES:
v1.14.7
Compare Source
1.14.7
November 30, 2023
CHANGES:
IMPROVEMENTS:
BUG FIXES:
log_requests_level
. [GH-24058]v1.14.6
Compare Source
1.14.6
November 09, 2023
SECURITY:
CHANGES:
FEATURES:
IMPROVEMENTS:
BUG FIXES:
on the request. [GH-23861]
These can now be configured individually with
detect_deadlocks
. [GH-23902]v1.14.5
Compare Source
1.14.5
October 25, 2023
CHANGES:
IMPROVEMENTS:
tls-server-name
arg for plugin registration [GH-23549]BUG FIXES:
partition could continue to write data to Consul after a new leader is elected
potentially causing data loss or corruption for keys with many concurrent
writers. For Enterprise clusters this could cause corruption of the merkle trees
leading to failure to complete merkle sync without a full re-index. [GH-23013]
v1.14.4
Compare Source
1.14.4
September 27, 2023
CHANGES:
IMPROVEMENTS:
BUG FIXES:
v1.14.3
Compare Source
1.14.3
September 13, 2023
SECURITY:
CHANGES:
FEATURES:
IMPROVEMENTS:
BUG FIXES:
table
. [GH-22818]v1.14.2
Compare Source
August 30, 2023
CHANGES:
IMPROVEMENTS:
BUG FIXES:
Also fix a related potential deadlock. [GH-21110]
sdk/ldaputil: use EscapeLDAPValue implementation from cap/ldap [GH-22249]
max_versions
default for secret metadata unintentionally overriding kv engine defaults [GH-22394]Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.