Code execution via malicious Git repository configuration
Published Mar 14, 2022 · Updated Apr 23, 2025
Command injection in fish 3.1.0 through 3.3.1 allows local users to execute arbitrary code through a malicious Git repository. The default fish_git_prompt function automatically invokes Git when entering a repository, and Git honors its per-repository core.fsmonitor command. Execution requires a user to change into an attacker-controlled directory, and repositories created by git clone are not affected by this trigger.
Summary
What happened
Command injection in fish 3.1.0 through 3.3.1 allows local users to execute arbitrary code through a malicious Git repository. The default fish_git_prompt function automatically invokes Git when entering a repository, and Git honors its per-repository core.fsmonitor command. Execution requires a user to change into an attacker-controlled directory, and repositories created by git clone are not affected by this trigger.
The record
- CVE
- CVE-2022-20001
- Published
- Mar 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- fish-shell
- Product
- fish
- Classifications
- CWE-427, CWE-74, T1204.002, T1059.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=>= 3.1.0, < 3.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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