Authenticated code execution via eval-parsed filenames
Published Jan 17, 2023 · Updated Apr 4, 2025
Code injection in Ruby/Git 1.2.0 through 1.12.0 allows remote authenticated users to execute arbitrary Ruby code through a crafted filename. The Git::Lib#ls_files method passes quoted paths from git ls-files to eval while unescaping them, so filename content becomes executable Ruby syntax. Exploitation requires the target to load an attacker-controlled repository and invoke file listing; successful injection runs code in the consuming process.
Summary
What happened
Code injection in Ruby/Git 1.2.0 through 1.12.0 allows remote authenticated users to execute arbitrary Ruby code through a crafted filename. The Git::Lib#ls_files method passes quoted paths from git ls-files to eval while unescaping them, so filename content becomes executable Ruby syntax. Exploitation requires the target to load an attacker-controlled repository and invoke file listing; successful injection runs code in the consuming process.
The record
- CVE
- CVE-2022-46648
- Published
- Jan 17, 2023
- Updated
- Apr 4, 2025
- Vendor
- ruby-git
- Product
- Ruby/Git
- Classifications
- CWE-94, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2023CVE publishedPublication date reported by the CVE source.
- Apr 4, 2025Record 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=versions prior to v1.13.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