ruby-git has potential remote code execution vulnerability
The git gem, between versions 1.2.0 and 1.12.0, incorrectly parsed the output of the `git ls-files` command using `eval()` to unescape quoted file names. If a file name was added to the git repository contained special characters, such as `\n`, then the `git ls-files` command would print the file name in quotes and escape any special characters. If the `Git#ls_files` method encountered a quoted file name it would use `eval()` to unquote and unescape any special characters, leading to potential remote code execution. Version 1.13.0 of the git gem was released which correctly parses any quoted file names.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-46648US | high8.0 | — | ||
ruby-git versions prior to v1.13.0 allows a remote authenticated attacker to execute an arbitrary ruby code by having a user to load a repository containing a specially crafted fil… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/ruby-git/ruby-gitPACKAGE
- https://github.com/ruby-git/ruby-git/pull/602WEB
- https://github.com/ruby-git/ruby-git/releases/tag/v1.13.0WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/git/CVE-2022-46648.ymlWEB
- https://jvn.jp/en/jp/JVN16765254/index.htmlWEB
- https://lists.debian.org/debian-lts-announce/2023/01/msg00043.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-46648ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan