# CVE-2023-49569: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients > A path traversal flaw in go-git allows attackers to write files outside the repository, potentially leading to remote code execution on affected clients. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jan 2024 - **Updated:** 14 Nov 2024 - **Also known as:** AZL-33891, AZL-35098, AZL-39592, DEBIAN-CVE-2023-49569, GHSA-449p-3h89-pw88, GO-2024-2456, RHSA-2024:2631, UBUNTU-CVE-2023-49569 ## What is CVE-2023-49569? CVE-2023-49569 is a critical path traversal vulnerability in go-git, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2023-49569? 6 open source packages ship an affected version, including github.com/go-git/go-git/v5 and gopkg.in/src-d/go-git.v4. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/go-git/go-git/v5` | Go | From 5.0.0 | 5.11.0 | | `github.com/go-git/go-git/v5` | Go | From 5.0.0 | 5.11.0 | | `github.com/go-git/go-git/v5` | Go | From 5.0.0 | 5.11.0 | | `gopkg.in/src-d/go-git.v4` | Go | From 4.0.0 to 4.13.1 | None | | `gopkg.in/src-d/go-git.v4` | Go | From 4.0.0 to 4.13.1 | None | | `gopkg.in/src-d/go-git.v4` | Go | From 4.7.1 | None | | `ceph` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-base` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-base-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-common` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-common-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-debugsource` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-exporter-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-fuse` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-fuse-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-immutable-object-cache` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-immutable-object-cache-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-mds-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-mgr-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-mib` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-mon-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-osd-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-radosgw-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-resource-agents` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-selinux` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `ceph-test-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `cephfs-mirror-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `cephfs-top` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libcephfs-devel` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libcephfs2` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libcephfs2-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libcephsqlite-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `librados-devel` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `librados-devel-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `librados2` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `librados2-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libradospp-devel` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libradosstriper1` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | | `libradosstriper1-debuginfo` | Red Hat:ceph_storage:6.1::el8 | All versions | 2:17.2.6-216.el8cp | Products: Go-Git Project Go-Git. ## How do I fix CVE-2023-49569? Upgrade github.com/go-git/go-git/v5 to 5.11.0 or later. ## Is CVE-2023-49569 being exploited? There is no known exploitation of CVE-2023-49569 in the wild and no public exploit code. ## Other vulnerabilities in go-git - [CVE-2025-21613](https://insights.sbomify.com/CVE-2025-21613/): go-git has an Argument Injection via the URL field (critical 9.2) - [CVE-2025-21614](https://insights.sbomify.com/CVE-2025-21614/): go-git clients vulnerable to DoS via maliciously crafted Git server replies (high 7.5) - [CVE-2023-49568](https://insights.sbomify.com/CVE-2023-49568/): Maliciously crafted Git server replies can cause DoS on go-git clients (high 7.5) - [CVE-2026-45022](https://insights.sbomify.com/CVE-2026-45022/): go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git (high 7.0) - [CVE-2026-45571](https://insights.sbomify.com/CVE-2026-45571/): go-git: Crafted repositories may modify main and submodule .git directories (medium 5.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-49569 and fix it if it is affected. What it is: CVE-2023-49569 is a critical path traversal vulnerability in go-git, published on 12 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-49569 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/go-git/go-git/v5 (Go): affected from 5.0.0; fixed in 5.11.0 - github.com/go-git/go-git/v5 (Go): affected from 5.0.0; fixed in 5.11.0 - github.com/go-git/go-git/v5 (Go): affected from 5.0.0; fixed in 5.11.0 - gopkg.in/src-d/go-git.v4 (Go): affected from 4.0.0 up to 4.13.1; no fix listed - gopkg.in/src-d/go-git.v4 (Go): affected from 4.0.0 up to 4.13.1; no fix listed - gopkg.in/src-d/go-git.v4 (Go): affected from 4.7.1; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-49569/ (Markdown: https://insights.sbomify.com/CVE-2023-49569/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49569 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49569 - OSV: https://osv.dev/vulnerability/CVE-2023-49569 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-49569/ Summaries are generated and may contain mistakes; the official description above is the record.