Skip to content

Commit bcc5798

Browse files
1 parent d776b8d commit bcc5798

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

advisories/github-reviewed/2025/12/GHSA-9xwc-hfwc-8w59/GHSA-9xwc-hfwc-8w59.json

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-9xwc-hfwc-8w59",
4-
"modified": "2025-12-17T22:50:29Z",
4+
"modified": "2025-12-20T05:17:54Z",
55
"published": "2025-12-17T22:50:29Z",
66
"aliases": [
77
"CVE-2025-68144"
88
],
99
"summary": " mcp-server-git argument injection in git_diff and git_checkout functions allows overwriting local files",
10-
"details": "In mcp-server-git versions prior to 2025.12.17, the git_diff and git_checkout functions passed user-controlled arguments directly to git CLI commands without sanitization. Flag-like values (e.g., `--output=/path/to/file` for `git_diff`) would be interpreted as command-line options rather than git refs, enabling arbitrary file overwrites. The fix adds validation that rejects arguments starting with - and verifies the argument resolves to a valid git ref via rev_parse before execution. Users are advised to update to 2025.12.17 resolve this issue when it is released.\n\nThank you to https://hackerone.com/yardenporat for reporting.",
10+
"details": "In mcp-server-git versions prior to 2025.12.18, the git_diff and git_checkout functions passed user-controlled arguments directly to git CLI commands without sanitization. Flag-like values (e.g., `--output=/path/to/file` for `git_diff`) would be interpreted as command-line options rather than git refs, enabling arbitrary file overwrites. The fix adds validation that rejects arguments starting with - and verifies the argument resolves to a valid git ref via rev_parse before execution. Users are advised to update to 2025.12.18 resolve this issue.\n\nThank you to https://hackerone.com/yardenporat for reporting.",
1111
"severity": [
1212
{
1313
"type": "CVSS_V4",
@@ -28,7 +28,7 @@
2828
"introduced": "0"
2929
},
3030
{
31-
"last_affected": "2025.11.25"
31+
"fixed": "2025.12.18"
3232
}
3333
]
3434
}
@@ -40,6 +40,10 @@
4040
"type": "WEB",
4141
"url": "https://github.com/modelcontextprotocol/servers/security/advisories/GHSA-9xwc-hfwc-8w59"
4242
},
43+
{
44+
"type": "ADVISORY",
45+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68144"
46+
},
4347
{
4448
"type": "PACKAGE",
4549
"url": "https://github.com/modelcontextprotocol/servers"
@@ -52,6 +56,6 @@
5256
"severity": "MODERATE",
5357
"github_reviewed": true,
5458
"github_reviewed_at": "2025-12-17T22:50:29Z",
55-
"nvd_published_at": null
59+
"nvd_published_at": "2025-12-17T23:16:04Z"
5660
}
5761
}

advisories/github-reviewed/2025/12/GHSA-j22h-9j4x-23w5/GHSA-j22h-9j4x-23w5.json

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-j22h-9j4x-23w5",
4-
"modified": "2025-12-17T22:50:38Z",
4+
"modified": "2025-12-20T05:18:27Z",
55
"published": "2025-12-17T22:50:38Z",
66
"aliases": [
77
"CVE-2025-68145"
88
],
99
"summary": "mcp-server-git has missing path validation when using --repository flag",
10-
"details": "In mcp-server-git versions prior to 2025.12.17, when the server is started with the --repository flag to restrict operations to a specific repository path, it did not validate that repo_path arguments in subsequent tool calls were actually within that configured path. This could allow tool calls to operate on other repositories accessible to the server process. The fix adds path validation that resolves both the configured repository and the requested path (following symlinks) and verifies the requested path is within the allowed repository before executing any git operations. Users are advised to upgrade to 2025.12.17 upon release to remediate this issue.\n\nThank you to https://hackerone.com/yardenporat for reporting.",
10+
"details": "In mcp-server-git versions prior to 2025.12.18, when the server is started with the --repository flag to restrict operations to a specific repository path, it did not validate that repo_path arguments in subsequent tool calls were actually within that configured path. This could allow tool calls to operate on other repositories accessible to the server process. The fix adds path validation that resolves both the configured repository and the requested path (following symlinks) and verifies the requested path is within the allowed repository before executing any git operations. Users are advised to upgrade to 2025.12.18 to remediate this issue.\n\nThank you to https://hackerone.com/yardenporat for reporting.",
1111
"severity": [
1212
{
1313
"type": "CVSS_V4",
@@ -28,7 +28,7 @@
2828
"introduced": "0"
2929
},
3030
{
31-
"last_affected": "2025.11.25"
31+
"fixed": "2025.12.18"
3232
}
3333
]
3434
}
@@ -40,6 +40,10 @@
4040
"type": "WEB",
4141
"url": "https://github.com/modelcontextprotocol/servers/security/advisories/GHSA-j22h-9j4x-23w5"
4242
},
43+
{
44+
"type": "ADVISORY",
45+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68145"
46+
},
4347
{
4448
"type": "PACKAGE",
4549
"url": "https://github.com/modelcontextprotocol/servers"
@@ -52,6 +56,6 @@
5256
"severity": "MODERATE",
5357
"github_reviewed": true,
5458
"github_reviewed_at": "2025-12-17T22:50:38Z",
55-
"nvd_published_at": null
59+
"nvd_published_at": "2025-12-17T23:16:04Z"
5660
}
5761
}

0 commit comments

Comments
 (0)