Arbitrary code execution via repository-controlled fsmonitor
Published Oct 13, 2022 · Updated May 15, 2025
Command injection in Powerline Gitstatus before 1.3.2 allows attackers to execute arbitrary code through a malicious Git repository. GitStatusSegment.get_base_command invokes Git without overriding repository-controlled core.fsmonitor, allowing Git to execute an attacker-supplied command. Exploitation requires a user to enter an attacker-controlled repository directory, after which commands run with that user's privileges.
Summary
What happened
Command injection in Powerline Gitstatus before 1.3.2 allows attackers to execute arbitrary code through a malicious Git repository. GitStatusSegment.get_base_command invokes Git without overriding repository-controlled core.fsmonitor, allowing Git to execute an attacker-supplied command. Exploitation requires a user to enter an attacker-controlled repository directory, after which commands run with that user's privileges.
The record
- CVE
- CVE-2022-42906
- Published
- Oct 13, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 13, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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