Remote code execution via ChrootOS path escape
Published Jan 12, 2024 · Updated Nov 14, 2024
Path traversal in go-git before 5.11.0 allows remote attackers to write arbitrary files through crafted Git server replies. ChrootOS handles paths from those replies without reliably confining resolved filesystem operations to its root. Exposure requires filesystem-backed ChrootOS, the default for PlainOpen and PlainClone; BoundOS and in-memory filesystems are unaffected, and file writes can lead to code execution.
Summary
What happened
Path traversal in go-git before 5.11.0 allows remote attackers to write arbitrary files through crafted Git server replies. ChrootOS handles paths from those replies without reliably confining resolved filesystem operations to its root. Exposure requires filesystem-backed ChrootOS, the default for PlainOpen and PlainClone; BoundOS and in-memory filesystems are unaffected, and file writes can lead to code execution.
The record
- CVE
- CVE-2023-49569
- Published
- Jan 12, 2024
- Updated
- Nov 14, 2024
- Vendor
- go-git
- Product
- go-git
- Classifications
- CWE-22, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.11.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo