dbcve.org
Go GitApplication · Go Git Project

CVE-2023-49568

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 5.11.0 or later.
See remediation →
84/100
Remediation priority · High
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 denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients. Applications using only the in-memory filesystem supported by go-git are not affected by this vulnerability. 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 · moderate confidence

go-git versions before v5.11 contain a DoS vulnerability where specially crafted responses from a malicious Git server can trigger resource exhaustion in clients. The vulnerability is triggered through filesystem operations when processing Git server responses, while applications using only the in-memory filesystem are not affected.

MitigationUpgrade go-git to v5.11 or later to remediate this vulnerability. Consider implementing network-level controls to validate Git server responses if immediate upgrade is not feasible.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 in use
    Run 'go list -m all' or inspect your go.mod file to find the version of github.com/go-git/go-git listed in dependencies
    Affected if The version shown is earlier than v5.11.0 (e.g., v5.10.0, v5.0.0, v4.x.x)
  2. Check for go-git as a transitive dependency
    Run 'go list -m -json all | grep -A2 go-git' to see if go-git is a transitive dependency even if not directly imported in your code
    Affected if go-git version earlier than v5.11.0 appears in the dependency tree
  3. Determine if filesystem operations are used
    Search your codebase for git.Clone, git.NewRemote, or similar calls that interact with local filesystem paths rather than purely in-memory Storage options
    Affected if Your code performs git operations that write to or read from the local filesystem (disk-based storage)
  4. Check for in-memory filesystem usage
    Review your code for use of gogitfs.New() or in-memory storage implementations - grep for 'gogitfs' or 'memory' in git-related code
    Affected if The codebase uses only in-memory filesystem storage (gogitfs.New()) and makes no filesystem-based git calls
  5. Verify runtime dependency version
    At runtime, import go-git and print the version: 'import _ "github.com/go-git/go-git/v5"; func init() { fmt.Println(git.Version) }' or check your vendored dependencies
    Affected if The runtime-loaded go-git library version is before v5.11.0

You are affected if go-git version earlier than v5.11.0 is in use AND your application performs filesystem-based git operations (disk storage), but NOT affected if using only in-memory filesystem storage.

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 to remediate this vulnerability. Consider implementing network-level controls to validate Git server responses if immediate upgrade is not feasible.

Recommended fix High confidence

5.11.0

  1. Check the current go-git version in your project's go.mod file
  2. Update the go-git dependency to version 5.11.0 or later using: go get github.com/go-git/go-git/v5@latest or go get github.com/go-git/go-git/[email protected]
  3. Run go mod tidy to clean up dependencies
  4. Verify the updated version is installed: go list -m github.com/go-git/go-git/v5
  5. Rebuild and test your application to ensure the upgrade does not break existing functionality

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

Fix this in Go Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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