-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update module github.com/hashicorp/vault to v1.14.1 [security] #4550
Merged
jliempt
merged 6 commits into
master
from
renovate/go-github.com/hashicorp/vault-vulnerability
Oct 13, 2023
Merged
fix(deps): update module github.com/hashicorp/vault to v1.14.1 [security] #4550
jliempt
merged 6 commits into
master
from
renovate/go-github.com/hashicorp/vault-vulnerability
Oct 13, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fd7130c
to
cdaad23
Compare
32c3c1a
to
fc4ab4c
Compare
33f7c84
to
b3397ea
Compare
7538e66
to
0bb2527
Compare
f06272a
to
5499067
Compare
96714d1
to
1e9f22b
Compare
1e9f22b
to
b016cbf
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
/it-go |
Kudos, SonarCloud Quality Gate passed! |
jliempt
approved these changes
Oct 13, 2023
andrew-kireev
pushed a commit
that referenced
this pull request
Oct 17, 2023
…ity] (#4550) * fix(deps): update module github.com/hashicorp/vault to v1.14.3 [security] * update to v1.14.1 instead due to Go version * github.com/hashicorp/vault@v1.14.1 * go mod tidy --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: jliempt <> Co-authored-by: Jordi van Liempt <35920075+jliempt@users.noreply.github.com>
maxatsap
pushed a commit
to maxatsap/jenkins-library
that referenced
this pull request
Jul 23, 2024
…ity] (SAP#4550) * fix(deps): update module github.com/hashicorp/vault to v1.14.3 [security] * update to v1.14.1 instead due to Go version * github.com/hashicorp/vault@v1.14.1 * go mod tidy --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: jliempt <> Co-authored-by: Jordi van Liempt <35920075+jliempt@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0
->v1.14.3
GitHub Vulnerability Alerts
CVE-2023-3462
HashiCorp's Vault and Vault Enterprise are vulnerable to user enumeration when using the LDAP auth method. An attacker may submit requests of existent and non-existent LDAP users and observe the response from Vault to check if the account is valid on the LDAP server. This vulnerability is fixed in Vault 1.14.1 and 1.13.5.
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.
Release Notes
hashicorp/vault (github.com/hashicorp/vault)
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]v1.14.1
Compare Source
July 25, 2023
CHANGES:
which will have access to some system backend paths that were previously only accessible in the root namespace. [GH-21215]
IMPROVEMENTS:
BUG FIXES:
auth/token/create
fields to avoid incorrect warnings about ignored parameters [GH-18556]respects
AWS_ROLE_ARN
,AWS_WEB_IDENTITY_TOKEN_FILE
, andAWS_ROLE_SESSION_NAME
. [GH-21951]no managed key found with uuid
. [GH-21316]default_critical_options
anddefault_extension
if left unchanged. [GH-21739]ed25519
) [GH-21926]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.