Skip to content
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

chore(deps): update dependency gruntwork-io/terragrunt to v0.71.1 #9248

Merged
merged 1 commit into from
Dec 21, 2024

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor 0.70.4 -> 0.71.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

gruntwork-io/terragrunt (gruntwork-io/terragrunt)

v0.71.1

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.71.0...v0.71.1

v0.71.0

Compare Source

🔧 Fixes

Terragrunt stdout and stderr streams have been adjusted to more closely align with what users expect when using a tool orchestrating OpenTofu/Terraform.

For more information, read the following docs.

🛠️ Breaking Changes

While a bugfix, if you were relying on the incorrect behavior Terragrunt used, redirecting OpenTofu/Terraform stdout to stderr, you will experience a breaking change in this release.

To avoid having this be a breaking release, you can either use Terragrunt stdout instead of stderr for inspecting OpenTofu/Terraform stdout, or you can use stream redirection to reproduce the buggy behavior.

terragrunt plan 1>&2

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.70.4...v0.71.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/terragrunt:0.71.1

📦 Image Reference ghcr.io/uniget-org/tools/terragrunt:0.71.1
digestsha256:8be0cc57dbbc98094bed1d7609de2cabda00200e56362e66bb24c5a72068ac2f
vulnerabilitiescritical: 0 high: 1 medium: 1 low: 1
platformlinux/amd64
size41 MB
packages243
critical: 0 high: 1 medium: 0 low: 0 golang.org/x/net 0.32.0 (golang)

pkg:golang/golang.org/x/[email protected]

high 8.7: CVE--2024--45338 Allocation of Resources Without Limits or Throttling

Affected range<0.33.0
Fixed version0.33.0
CVSS Score8.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Description

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

critical: 0 high: 0 medium: 1 low: 1 github.com/aws/aws-sdk-go 1.55.5 (golang)

pkg:golang/github.com/aws/[email protected]

medium : CVE--2020--8911

Affected range>=0
Fixed versionNot Fixed
Description

A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

low : CVE--2020--8912

Affected range>=0
Fixed versionNot Fixed
Description

A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

Copy link

Copy link

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/12441159087.

@github-actions github-actions bot merged commit d6fefbf into main Dec 21, 2024
10 checks passed
@github-actions github-actions bot deleted the renovate/gruntwork-io-terragrunt-0.x branch December 21, 2024 01:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants