Billy: Path traversal vulnerabilities
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 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.
From the CVE record · GitHub_M
Multiple go-billy components insufficiently sanitize paths or enforce directory boundaries. An attacker who can supply crafted paths may cause applications relying on go-billy for isolation to access unintended filesystem locations. The input does not specify whether authentication or user interaction is required.
Check Go 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.