dbcve.org
Go GitApplication · Go Git Project

CVE-2023-49569

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 5.11.0 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
A path traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved. Applications are only affected if they are using the ChrootOS https://pkg.go.dev/github.com/go-git/go-billy/v5/osfs#ChrootOS , which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS https://pkg.go.dev/github.com/go-git/go-billy/v5/osfs#BoundOS  or in-memory filesystems are not affected by this issue. This is a go-git implementation issue and does not affect the upstream git cli.

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 · high confidence

A path traversal vulnerability in go-git versions prior to v5.11 allows attackers to create and modify files outside the intended directory when using ChrootOS (the default filesystem for Plain* functions like PlainClone). This can lead to arbitrary file write and potentially remote code execution.

MitigationUpgrade go-git to v5.11 or later, or explicitly use BoundOS instead of ChrootOS for filesystem operations.

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 GitApplication
Affected:>= 4.0.0, < 5.11.0

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
High

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

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. Identify go-git version
    Run 'go list -m all | grep go-git' or inspect your go.mod file for the go-git module version
    Affected if version is >= 4.0.0 and < 5.11.0
  2. Find Plain* function usage
    Search codebase for calls to PlainClone, PlainInit, PlainOpen, or PlainRootedClone functions from go-git
    Affected if any Plain* functions from go-git are used in the codebase
  3. Check filesystem type in use
    Inspect the code where the Plain* filesystem is created. Look for explicit use of BoundOS vs ChrootOS, or examine if the default filesystem is being used (ChrootOS is the default for Plain* functions)
    Affected if ChrootOS is being used (or no explicit BoundOS configuration exists)
  4. Determine if repositories are untrusted
    Review whether the code clones or opens repositories from untrusted sources (e.g., user input, external URLs, untrusted paths)
    Affected if the application processes repositories from untrusted or user-controlled sources

You are affected if go-git version is below v5.11 AND your code uses Plain* functions (which default to ChrootOS) to handle repositories from untrusted sources.

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 5.11.0 or later
Fixed in 5.11.0
Interim mitigation

Upgrade go-git to v5.11 or later, or explicitly use BoundOS instead of ChrootOS for filesystem operations.

Recommended fix High confidence

go-git v5.11.0 or later

  1. Verify your application uses ChrootOS (default when using PlainClone or PlainOpen functions) - check your codebase for imports of github.com/go-git/go-billy/v5/osfs and usage of Plain* functions
  2. Update go-git dependency to version 5.11.0 or later in your go.mod file (e.g., go get github.com/go-git/go-git/[email protected] or later)
  3. Run go mod tidy to update dependencies
  4. Rebuild your application to include the fixed version
  5. Redeploy your application

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

Fix this in Go Git Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49569 — 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-2023-49569 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