Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/hashicorp/go-slug

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5GoPublished

    HashiCorp go-slug Vulnerable to Zip Slip Attack

    CVE-2025-0377 · GHSA-wpfp-cm49-9m9q

    Affected
    • Go github.com/hashicorp/go-slug < 0.16.3
    Fixed in
    0.16.3· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 0.16.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5GoPublished

    Unsafe tar unpacking in HashiCorp go-slug

    CVE-2020-29529 · GHSA-2g5j-5x95-r6hr

    Affected
    • Go github.com/hashicorp/go-slug < 0.5.0
    Fixed in
    0.5.0· Vendor fix available
    Issue
    HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.

    Recommended action: Upgrade to 0.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →