go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
go-git
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-git/go-git/v6 Go |
|
|
| github.com/go-git/go-git/v5 Go |
|
|
go-git
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-git/go-git/v6 Go |
|
|
| github.com/go-git/go-git/v5 Go |
|
|
go-git is an extensible git implementation library written in pure Go. Prior to 5.19.0 and 6.0.0-alpha.3, go-git may parse malformed Git objects in a way that differs from upstream Git. When commit or tag objects contain ambiguous or malformed headers, go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object. Additionally, go-git’s commit signing and verification logic operates over commit data reconstructed from go-git’s parsed representation rather than the original raw object bytes. As a result, go-git may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository. This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed. This vulnerability is fixed in 5.19.0 and 6.0.0-alpha.3.
From the CVE record · GitHub_M
go-git can interpret malformed commit or tag headers differently from upstream Git. When it processes such objects, its signing and verification logic may use reconstructed commit data instead of the raw object bytes, making a signature appear valid even when the displayed or effective metadata differs from what was intended to be signed. The input does not specify whether authentication or user interaction is required.
Check applications using github.com/go-git/go-git/v5 before 5.19.0 or github.com/go-git/go-git/v6 from 6.0.0-alpha.1 up to, but not including, 6.0.0-alpha.3.