fix(deps): update module github.com/hashicorp/go-slug to v0.16.3 [security] #63
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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:
v0.15.2->v0.16.3GitHub Vulnerability Alerts
CVE-2025-0377
Summary
HashiCorp’s go-slug library is vulnerable to a zip-slip style attack when a non-existing user-provided path is extracted from the tar entry. This vulnerability, identified as CVE-2025-0377, is fixed in go-slug 0.16.3.
Background
HashiCorp’s go-slug shared library offers functions for packing and unpacking Terraform Enterprise compatible slugs. Slugs are gzip compressed tar files containing Terraform configuration files.
Details
When go-slug performs an extraction, the filename/extraction path is taken from the tar entry via the header.Name. It was discovered that the unpacking step improperly validated paths, potentially leading to path traversal, allowing an attacker to write an arbitrary file during extraction.
Remediation
Consumers of the go-slug shared library should evaluate the risk associated with this issue in the context of their go-slug usage and upgrade go-slug to 0.16.3 or later.
Release Notes
hashicorp/go-slug (github.com/hashicorp/go-slug)
v0.16.3Compare Source
What's Changed
Full Changelog: hashicorp/go-slug@v0.16.2...v0.16.3
v0.16.2Compare Source
What's Changed
AllowSymlinkTargetby @NodyHub in https://github.com/hashicorp/go-slug/pull/74New Contributors
Full Changelog: hashicorp/go-slug@v0.16.1...v0.16.2
v0.16.1Compare Source
sourcebundlepackage when RegistryMeta and Packages aren't the same size.Full Changelog: hashicorp/go-slug@v0.16.0...v0.16.1
v0.16.0Compare Source
.Append(...)function from thesourcebundlediagnostics API. Consumers should instead use the built-in golangappend()function. This ensures type-safety as you can't attempt to insert an invalid object into the diagnostics using the built-in function.Note: this is technically a breaking change for consumers of the
sourcebundlepackage since it removes a method, but we had previously marked it as experimental in the v0.12.0 release and warned that its API is subject to change. The package continues to be experimental and may change further before stabilizing.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 was generated by Mend Renovate. View the repository job log.