go-billy: Lack of depth and cycle detection in symlink resolution may lead to infinite loops and resource exhaustion
go-git go-billy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-git/go-billy/v5 Go |
|
|
| github.com/go-git/go-billy/v6 Go |
|
|
go-git go-billy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-git/go-billy/v5 Go |
|
|
| github.com/go-git/go-billy/v6 Go |
|
|
Billy is an interface filesystem abstraction for Go. Prior to versions 5.9.0 and 6.0.0-alpha.1, multiple components may improperly handle crafted or malformed input, resulting in panics, infinite loops, uncontrolled recursion, or excessive resource consumption. These issues arise from insufficient validation and missing safety mechanisms such as cycle detection, recursion limits, or defensive handling of unexpected states when processing untrusted repository data and filesystem structures. This issue has been patched in versions 5.9.0 and 6.0.0-alpha.1.
From the CVE record · GitHub_M
Affected go-billy components may mishandle crafted repository data or filesystem structures, causing panics, infinite loops, uncontrolled recursion, or excessive resource consumption. An attacker may trigger these failures if an application processes untrusted input; the input does not specify network access, authentication requirements, or user interaction.
Check applications using github.com/go-git/go-billy/v5 before 5.9.0 or github.com/go-git/go-billy/v6 before 6.0.0-alpha.1.