dbcve.org
Go SlugApplication · Hashicorp

CVE-2025-0377

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 0.16.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HashiCorp’s go-slug library contains a path traversal vulnerability (zip-slip style) during tar extraction. When extracting entries, the library fails to properly validate that extracted paths remain within the intended target directory, allowing attackers to craft malicious tar archives with relative path traversal sequences (../) to write files to arbitrary locations on the filesystem.

MitigationUpgrade to the patched version of go-slug library. As a critical (9.1) vulnerability, immediate patching is required. If patching is not immediately possible, avoid extracting untrusted tar archives or implement external path validation before extraction.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Go SlugApplication
Affected:< 0.16.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate go-slug library in your project
    Search your project for go-slug usage: check go.mod for 'go-slug' or 'github.com/hashicorp/go-slug' in dependencies, or look for the library in vendor/ or third_party directories
    Affected if go-slug library is present in dependencies or vendored code
  2. Identify installed go-slug version
    Run 'go list -m all | grep go-slug' or 'go mod graph | grep go-slug' to see the resolved version, or check the version tag in vendor/github.com/hashicorp/go-slug/ if vendored
    Affected if version is lower than 0.16.3 (e.g., 0.16.2, 0.15.0, etc.)
  3. Find tar extraction code using go-slug
    Search your codebase for calls to slug.Extract, slug.Unpack, or similar extraction functions from the go-slug package, or for usage of ReadFrom on a slug.Resolver
    Affected if code uses go-slug extraction functions to unpack tar archives
  4. Determine source of tar archives
    Review where the tar archives being extracted originate from - check if they come from user uploads, external URLs, untrusted network sources, or potentially malicious input
    Affected if tar archives from untrusted or external sources are being extracted using go-slug

You are affected if your project uses go-slug version below 0.16.3 and extracts tar archives from untrusted or external sources using the library's extraction functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.16.3 or later
Fixed in 0.16.3
Interim mitigation

Upgrade to the patched version of go-slug library. As a critical (9.1) vulnerability, immediate patching is required. If patching is not immediately possible, avoid extracting untrusted tar archives or implement external path validation before extraction.

Recommended fix High confidence

go-slug v0.16.3 or later

  1. Update the go-slug dependency to version 0.16.3 or later using 'go get github.com/hashicorp/[email protected]' (or a later stable release)
  2. Run 'go mod tidy' to clean up dependencies and verify the update
  3. Rebuild the application to incorporate the fixed library version
  4. Test the application to confirm the zip-slip vulnerability is mitigated and that normal functionality is preserved
Caveat Review the go-slug changelog between your current version and 0.16.3 for any breaking changes that may affect your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Slug Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0377 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data