CVE-2025-54584 Details
Description
GitProxy is an application that stands between developers and a Git remote endpoint (e.g., github.com). In versions 1.19.1 and below, an attacker can craft a malicious Git packfile to exploit the PACK signature detection in the parsePush.ts file. By embedding a misleading PACK signature within commit content and carefully constructing the packet structure, the attacker can trick the parser into treating invalid or unintended data as the packfile. Potentially, this would allow bypassing approval or hiding commits. This issue is fixed in version 1.19.2.
A vulnerability exists in GitProxy versions 1.19.1 and earlier, specifically within the PACK signature detection of the parsePush processor. By crafting a malicious Git packfile that includes a misleading PACK signature embedded in commit content, an attacker can manipulate the parser into accepting invalid data as a legitimate packfile. This exploitation could bypass approval processes or obscure commits, potentially allowing unauthorized changes to be made in repositories protected by GitProxy.
Users are advised to upgrade to GitProxy version 1.19.2 or 2.0.0, both of which include patches for this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-115 | Misinterpretation of Input | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| finos gitproxy | < 1.19.2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 1, 2025 | Initial Analysis | [email protected] |
| Jul 30, 2025 | New CVE Received | [email protected] |