CVE-2025-54584: @finos/git proxy GitProxy Backfile Parsing Exploit Vulnerability

HIGH
Advisory Identifier: GHSA-xxmh-rf63-qwjv
CWE-115
Published
Advisory Summary

CVE-2025-54584 is a HIGH gitproxy backfile parsing exploit vulnerability (CWE-115: Misinterpretation of Input) affecting @finos/git proxy libraries in the npm ecosystem. The issue involves gitproxy backfile parsing exploit. Remediation is available by upgrading affected packages to version 1.19.2.

CVE-2025-54584 at a Glance

CVE Identifier CVE-2025-54584
GHSA Identifier GHSA-xxmh-rf63-qwjv
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-115: Misinterpretation of Input
Affected Product @finos/git proxy
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-54584

To remediate this vulnerability, upgrade all affected @finos/git proxy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@finos/git-proxy fixed: 1.19.2
npm install @finos/git-proxy@1.19.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @finos/git-proxy

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-54584, inspect your project dependencies using npm:

npm ls @finos/git-proxy

Analyze the terminal output to locate any version of @finos/git proxy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.19.2), your application is affected.

Note: The npm ls @finos/git-proxy command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-115: Misinterpretation of Input, where the product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion. In @finos/git proxy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary An attacker can craft a malicious Git packfile to exploit the PACK signature detection in the `parsePush.ts`. 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. ### Details The affected version of `parsePush.ts` attempts to locate the Git PACK file by looking for the last occurrence of the string "PACK" in the incoming push payload: ```ts const packStart = buffer.lastIndexOf('PACK'); ``` This assumes that any "PACK" string near the end of the push is the beginning of the actual binary Git packfile. However, Git objects (commits, blobs, etc.) can contain arbitrary content (including the word PACK) in binary or non-compressed blobs. An attacker could abuse this by: 1. Crafting a custom packfile using low-level Git tools or by manually forging one 2. Placing the string "PACK" inside a commit body or a binary file blob that appears after the real PACK start in the stream. The parser then ignores the actual push and treats the binary blob/commit body as the PACK file. The actual push contents may violate existing push policies. ### PoC 1. Make a commit on any branch (example: `test-branch`) containing the string "PACK" 2. Manually generate a custom packfile with both branches using `git pack-objects` or a low-level library/custom script: a) Add the string "PACK" after the real packfile's PACK header in the binary stream 3. Push using a custom client/raw protocol injection ### Impact Attackers with push access can hide commits from scanning/approval and make changes that bypass policies, potentially inserting unwanted/malicious code into a GitProxy protected repository. The vulnerability impacts all users or organizations relying on GitProxy to enforce policies and prevent unapproved changes. It requires no elevated privileges beyond regular push access, and no extra user interaction, however, it does require a considerable amount of technical skill and intentional effort to accomplish.

CVE-2025-54584 Affected @finos/git proxy Versions

1 component(s)
Fixed Versions:
1.19.2
Product / Package Ecosystem Affected Versions Fixed Version
@finos/git-proxy
npm
< 1.19.2
1.19.2

References

Frequently Asked Questions

What is CVE-2025-54584?
CVE-2025-54584 is a security vulnerability in @finos/git proxy involving GitProxy Backfile Parsing Exploit under CWE-115: Misinterpretation of Input.
Which @finos/git proxy versions are affected?
Affected versions include releases prior to 1.19.2 across affected packages: @finos/git-proxy.
What version fixes CVE-2025-54584?
Upgrading to 1.19.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @finos/git-proxy affected?
Yes, @finos/git-proxy is affected in releases prior to 1.19.2. Upgrade your dependency to 1.19.2 or later.
What CWE is associated with CVE-2025-54584?
CVE-2025-54584 is classified under CWE-115: Misinterpretation of Input (The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.).
How can I check npm dependencies for CVE-2025-54584?
Run the dependency tree command: 'npm ls @finos/git-proxy'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xxmh-rf63-qwjv",
  "modified" : "2025-07-31T11:18:40Z",
  "published" : "2025-07-30T16:40:07Z",
  "aliases" : [ "CVE-2025-54584" ],
  "summary" : "GitProxy Backfile Parsing Exploit",
  "details" : "### Summary\nAn attacker can craft a malicious Git packfile to exploit the PACK signature detection in the `parsePush.ts`. 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.\n\n### Details\nThe affected version of `parsePush.ts` attempts to locate the Git PACK file by looking for the last occurrence of the string \"PACK\" in the incoming push payload:\n\n```ts\nconst packStart = buffer.lastIndexOf('PACK');\n```\n\nThis assumes that any \"PACK\" string near the end of the push is the beginning of the actual binary Git packfile. However, Git objects (commits, blobs, etc.) can contain arbitrary content (including the word PACK) in binary or non-compressed blobs.\n\nAn attacker could abuse this by:\n1. Crafting a custom packfile using low-level Git tools or by manually forging one\n2. Placing the string \"PACK\" inside a commit body or a binary file blob that appears after the real PACK start in the stream.\n\nThe parser then ignores the actual push and treats the binary blob/commit body as the PACK file. The actual push contents may violate existing push policies.\n\n### PoC\n\n1. Make a commit on any branch (example: `test-branch`) containing the string \"PACK\"\n2. Manually generate a custom packfile with both branches using `git pack-objects` or a low-level library/custom script:\n  a) Add the string \"PACK\" after the real packfile's PACK header in the binary stream\n3. Push using a custom client/raw protocol injection\n\n### Impact\n\nAttackers with push access can hide commits from scanning/approval and make changes that bypass policies, potentially inserting unwanted/malicious code into a GitProxy protected repository.\n\nThe vulnerability impacts all users or organizations relying on GitProxy to enforce policies and prevent unapproved changes. It requires no elevated privileges beyond regular push access, and no extra user interaction, however, it does require a considerable amount of technical skill and intentional effort to accomplish.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@finos/git-proxy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.19.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.19.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/finos/git-proxy/security/advisories/GHSA-xxmh-rf63-qwjv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-54584"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/finos/git-proxy/commit/333c98a165a5a1ec88414db3d4a2c6f81e083e0f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/finos/git-proxy/commit/a620a2f33c39c78e01783a274580bf822af3cc3a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/finos/git-proxy"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/finos/git-proxy/releases/tag/v1.19.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-115" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-30T16:40:07Z",
    "nvd_published_at" : "2025-07-30T20:15:38Z"
  }
}