A critical OS command injection vulnerability in GitList 2.0.0 allows remote, unauthenticated attackers to execute arbitrary code on the underlying server.

The application incorrectly handles Git dubious ownership errors by globally setting safe.directory='*', which bypasses security boundaries and allows an attacker to force the execution of repository-controlled diff or textconv helpers during standard Git operations. This vulnerability is remotely exploitable without authentication, as the trigger occurs during routine repository browsing and commit viewing.

Successful exploitation of this vulnerability grants an attacker the ability to execute arbitrary commands with the privileges of the web service user. This creates a high risk of total system compromise, unauthorized access to sensitive source code repositories, and potential lateral movement within the network. With a CVSS score of 7.3, this flaw represents a significant threat to organizational data integrity and infrastructure availability.

Immediate Action: Upgrade to version 3.0.0-beta or later immediately, as this version contains the necessary logic changes to secure the Git command execution environment.

Proactive Monitoring: Review web server and system access logs for anomalous requests targeting repository commit views, specifically looking for attempts to interact with Git configuration or external scripts.

Compensating Controls: Deploy a Web Application Firewall (WAF) to block malicious requests containing suspicious Git-related payloads, although this should be treated as a temporary measure until the patch is applied.

Public Exploit Available: Yes — a public proof-of-concept and detailed exploitation chain are available via the official project issue tracker (GitHub issue 947).

The severity of this remote code execution vulnerability necessitates immediate action. Administrators must prioritize updating GitList to version 3.0.0-beta to eliminate the root cause of the trust-boundary failure. Given the availability of a functional proof-of-concept, the risk of exploitation is elevated and requires a swift response to prevent potential unauthorized access and system compromise.