unistack-org/micro-config-vault
4
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

Bump github.com/hashicorp/vault/api from 1.3.0 to 1.3.1 #48

Merged
dependabot[bot] merged 1 commits from dependabot/go_modules/github.com/hashicorp/vault/api-1.3.1 into master 2022-01-12 15:32:33 +03:00
Conversation 2 Commits 1 Files Changed 2 +3 -4
dependabot[bot] commented 2021-12-23 11:28:35 +03:00 (Migrated from github.com)
Copy Link

Bumps github.com/hashicorp/vault/api from 1.3.0 to 1.3.1.

Changelog

Sourced from github.com/hashicorp/vault/api's changelog.

1.3.10

August 27th, 2020

NOTE:

All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users.

BUG FIXES:

  • auth/aws: Made header handling for IAM authentication more robust

1.3.9.1

August 21st, 2020

Enterprise Only

NOTE:

Includes correct license in the HSM binary.

1.3.9

August 20th, 2020

NOTE:

OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected.

KNOWN ISSUES:

  • AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the 1.3.9 Upgrade Guide
  • In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1.

1.3.8

August 20th, 2020

SECURITY:

  • When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero)
  • When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero)

KNOWN ISSUES:

  • OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected.
  • AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the 1.3.8 Upgrade Guide

1.3.7

July 2nd, 2020

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps [github.com/hashicorp/vault/api](https://github.com/hashicorp/vault) from 1.3.0 to 1.3.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/hashicorp/vault/blob/main/CHANGELOG.md">github.com/hashicorp/vault/api's changelog</a>.</em></p> <blockquote> <h2>1.3.10</h2> <h3>August 27th, 2020</h3> <p>NOTE:</p> <p>All security content from 1.5.2, 1.5.1, 1.4.5, 1.4.4, 1.3.9, 1.3.8, 1.2.6, and 1.2.5 has been made fully open source, and the git tags for 1.5.3, 1.4.6, 1.3.10, and 1.2.7 will build correctly for open source users.</p> <p>BUG FIXES:</p> <ul> <li>auth/aws: Made header handling for IAM authentication more robust</li> </ul> <h2>1.3.9.1</h2> <h3>August 21st, 2020</h3> <h3>Enterprise Only</h3> <p>NOTE:</p> <p>Includes correct license in the HSM binary.</p> <h2>1.3.9</h2> <h3>August 20th, 2020</h3> <p>NOTE:</p> <p>OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected.</p> <p>KNOWN ISSUES:</p> <ul> <li>AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the <a href="https://www.vaultproject.io/docs/upgrading/upgrade-to-1.3.9">1.3.9 Upgrade Guide</a></li> <li>In versions 1.2.6, 1.3.9, 1.4.5, and 1.5.2, enterprise licenses on the HSM build were not incorporated correctly - enterprise customers should use 1.2.6.1, 1.3.9.1, 1.4.5.1, and 1.5.2.1.</li> </ul> <h2>1.3.8</h2> <h3>August 20th, 2020</h3> <p>SECURITY:</p> <ul> <li>When using the IAM AWS Auth Method, under certain circumstances, values Vault uses to validate identities and roles can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.7.1 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16250) (Discovered by Felix Wilhelm of Google Project Zero)</li> <li>When using the GCP GCE Auth Method, under certain circumstances, values Vault uses to validate GCE VMs can be manipulated and bypassed. This vulnerability affects Vault and Vault Enterprise 0.8.3 and newer and is fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1 (CVE-2020-16251) (Discovered by Felix Wilhelm of Google Project Zero)</li> </ul> <p>KNOWN ISSUES:</p> <ul> <li>OSS binaries of 1.5.1, 1.4.4, 1.3.8, and 1.2.5 were built without the Vault UI. Enterprise binaries are not affected.</li> <li>AWS IAM logins may return an error depending on the headers sent with the request. For more details and a workaround, see the <a href="https://www.vaultproject.io/docs/upgrading/upgrade-to-1.3.8">1.3.8 Upgrade Guide</a></li> </ul> <h2>1.3.7</h2> <h3>July 2nd, 2020</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/hashicorp/vault/commit/cec3fdeda0077efb0a6b0343908322f806a1dfef"><code>cec3fde</code></a> release: stage v1.3.1</li> <li><a href="https://github.com/hashicorp/vault/commit/37660a048dc1fd1450e1b1a49c5cc6ded6464ea0"><code>37660a0</code></a> Missing cherry picks 1.3.1 (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8051">#8051</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/6e06873f6aacc03210048d33587d1d02595f44af"><code>6e06873</code></a> Update SDK for 1.3.1</li> <li><a href="https://github.com/hashicorp/vault/commit/06959d23b5025e41d55e1dd5c14a153e4441e63d"><code>06959d2</code></a> Update release version</li> <li><a href="https://github.com/hashicorp/vault/commit/e6b6efb4e20eb8443b3541c019da53a4337078e9"><code>e6b6efb</code></a> Update AD plugin to v0.6.2</li> <li><a href="https://github.com/hashicorp/vault/commit/7c7ae5018bf6ac4d5d5f37308ede3a5742dcad11"><code>7c7ae50</code></a> Avoid potential panic in LDAP client (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8047">#8047</a>) (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8048">#8048</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/bba89623be214a2e973b61be37b1f536cf8d14f1"><code>bba8962</code></a> Update plugin deps for 1.3.1 (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8030">#8030</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/0e489352090c1fe47d8168ce703fb7f0e3238447"><code>0e48935</code></a> ci: bump go to 1.12.14</li> <li><a href="https://github.com/hashicorp/vault/commit/06bce3f223955b3ba983dcc7eafcc55c99da395d"><code>06bce3f</code></a> Fix identity token panic during invalidation (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8015">#8015</a>) (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/8043">#8043</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/9d51b36f3ae4700c4404049d9e35ed62831d8d8a"><code>9d51b36</code></a> Add an sts_region parameter to the AWS auth engine's client config (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/7922">#7922</a>) (#...</li> <li>Additional commits viewable in <a href="https://github.com/hashicorp/vault/compare/v1.3.0...v1.3.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/hashicorp/vault/api&package-manager=go_modules&previous-version=1.3.0&new-version=1.3.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
vtolstov commented 2021-12-29 00:47:53 +03:00 (Migrated from github.com)
Copy Link

@dependabot recreate

@dependabot recreate
👍 1
vtolstov (Migrated from github.com) approved these changes 2022-01-11 11:26:58 +03:00
Sign in to join this conversation.
Reviewers
No Reviewers
vtolstov
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
atolstikhin devstigneev pugnack vtolstov
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unistack-org/micro-config-vault#48
Delete Branch "dependabot/go_modules/github.com/hashicorp/vault/api-1.3.1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?