Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-59831: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in snowyu git-commiters.js

0
High
VulnerabilityCVE-2025-59831cvecve-2025-59831cwe-77cwe-78
Published: Thu Sep 25 2025 (09/25/2025, 13:34:02 UTC)
Source: CVE Database V5
Vendor/Project: snowyu
Product: git-commiters.js

Description

git-commiters is a Node.js function module providing committers stats for their git repository. Prior to version 0.1.2, there is a command injection vulnerability in git-commiters. This vulnerability manifests with the library's primary exported API: gitCommiters(options, callback) which allows specifying options such as cwd for current working directory and revisionRange as a revision pointer, such as HEAD. However, the library does not sanitize for user input or practice secure process execution API to separate commands from their arguments and as such, uncontrolled user input is concatenated into command execution. This issue has been patched in version 0.1.2.

AI-Powered Analysis

AILast updated: 09/25/2025, 13:46:14 UTC

Technical Analysis

CVE-2025-59831 is a high-severity command injection vulnerability affecting versions of the Node.js module git-commiters prior to 0.1.2. Git-commiters is a utility designed to provide statistics about committers in a git repository, exposing an API function gitCommiters(options, callback). This function accepts parameters such as cwd (current working directory) and revisionRange (a git revision pointer like HEAD). The vulnerability arises because the module improperly handles user-supplied input by concatenating it directly into shell commands without adequate sanitization or use of secure process execution APIs that separate commands from their arguments. This improper neutralization of special elements (CWE-77 and CWE-78) enables an attacker to inject arbitrary shell commands, which the system executes with the privileges of the running process. The vulnerability does not require authentication but does require user interaction (e.g., invoking the vulnerable API with crafted input). The CVSS 4.0 score of 8.7 reflects the high impact on confidentiality, integrity, and availability, as successful exploitation can lead to arbitrary code execution, data compromise, or system disruption. The issue was patched in version 0.1.2 by properly sanitizing inputs and adopting secure command execution practices. No known exploits are currently reported in the wild, but the severity and ease of exploitation make it a critical risk for environments using vulnerable versions of git-commiters, especially in automated CI/CD pipelines or developer tools that process untrusted input.

Potential Impact

For European organizations, this vulnerability poses a significant risk, particularly for software development teams and DevOps environments relying on git-commiters for repository analytics. Exploitation can lead to arbitrary command execution on developer workstations, build servers, or continuous integration systems, potentially allowing attackers to escalate privileges, exfiltrate sensitive source code, inject malicious code into repositories, or disrupt development workflows. The compromise of source code integrity and confidentiality can have cascading effects on product security and compliance with European data protection regulations such as GDPR. Additionally, organizations with automated deployment pipelines that incorporate git-commiters may face service outages or supply chain attacks if exploited. Given the widespread use of Node.js in European tech sectors, and the integration of git tools in development environments, the vulnerability could affect a broad range of companies, from startups to large enterprises.

Mitigation Recommendations

European organizations should immediately audit their software dependencies to identify any usage of git-commiters versions prior to 0.1.2. They must upgrade all instances of git-commiters to version 0.1.2 or later, where the vulnerability is patched. For environments where immediate upgrade is not feasible, implement strict input validation and sanitization on any user-supplied parameters passed to git-commiters, avoiding direct shell command concatenation. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to monitor for suspicious command execution patterns. Restrict permissions of processes running git-commiters to the minimum necessary, limiting potential damage from exploitation. Incorporate security scanning tools in CI/CD pipelines to detect vulnerable dependencies automatically. Finally, educate development and DevOps teams about the risks of command injection and secure coding practices, emphasizing the importance of using secure APIs for process execution.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-09-22T14:34:03.471Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d54789ac522a786501f6a6

Added to database: 9/25/2025, 1:45:45 PM

Last enriched: 9/25/2025, 1:46:14 PM

Last updated: 10/7/2025, 1:41:09 PM

Views: 22

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats