GHSA-382c-vx95-w3p5: Gittensory Missing Contributor-scoped Access Control On Vulnerability
MODERATEGHSA-382c-vx95-w3p5 is a MODERATE (CVSS 6.5) missing contributor-scoped access control on vulnerability (CWE-284: Improper Access Control) affecting Gittensory libraries in the npm ecosystem. The issue involves missing contributor-scoped access control on profile endpoint and mcp tool leaks miner financial data. Remediation is available in the latest vendor maintenance releases.
GHSA-382c-vx95-w3p5 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
How to Fix GHSA-382c-vx95-w3p5
To remediate this vulnerability, upgrade all affected Gittensory dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @jsonbored/gittensory-mcp@Latest secure releaseRun the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @jsonbored/gittensory-mcpHow to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-382c-vx95-w3p5, inspect your project dependencies using npm:
npm ls @jsonbored/gittensory-mcpAnalyze the terminal output to locate any version of Gittensory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The npm ls @jsonbored/gittensory-mcp 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-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Gittensory, 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
GHSA-382c-vx95-w3p5 Affected Gittensory Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@jsonbored/gittensory-mcp
|
npm |
≤ 0.1.0
|
|
References
Frequently Asked Questions
What is GHSA-382c-vx95-w3p5?
Which Gittensory versions are affected?
What version fixes GHSA-382c-vx95-w3p5?
Is @jsonbored/gittensory-mcp affected?
What is the CVSS score of GHSA-382c-vx95-w3p5?
What CWE is associated with GHSA-382c-vx95-w3p5?
How can I check npm dependencies for GHSA-382c-vx95-w3p5?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-382c-vx95-w3p5",
"modified" : "2026-07-09T13:44:51Z",
"published" : "2026-07-09T13:44:51Z",
"aliases" : [ ],
"summary" : "Gittensory: Missing contributor-scoped access control on profile endpoint and MCP tool leaks miner financial data",
"details" : "### Summary\n \n`GET /v1/contributors/:login/profile` and the `gittensory_get_contributor_profile` MCP tool skip the contributor-scoped access check that every sibling endpoint enforces. Any authenticated session/API/MCP token holder can read any contributor's profile; for confirmed Gittensor miners that exposes `alphaPerDay`, `taoPerDay`, `usdPerDay` (and the `hotkey` on the REST path). Authenticated cross-contributor disclosure, CWE-284 / IDOR.\n \n### Details\n \nIn `src/api/routes.ts` the profile handler returns `buildContributorProfile(...)` with no `requireContributorAccess` call. Every sibling (`/decision-pack`, `/repos/:owner/:repo/decision`, etc.) gates and 403s on a cross-contributor request — the profile route is the only omission. `buildContributorProfile` (`src/signals/engine.ts`) embeds `hotkey` and the three `*PerDay` fields for any confirmed miner.\n \nThe MCP tool `getContributorProfile` (`src/mcp/server.ts`) also omits `requireContributorAccess`. Its `redactSensitiveForMcp` filter only strips keys matching `hotkey|coldkey|wallet|private_key|privateKey|mnemonic`, so the hotkey is dropped but `alphaPerDay`/`taoPerDay`/`usdPerDay` pass through.\n \nThe codebase treats these as secret everywhere else — `decision-pack.ts` destructures the hotkey out before serving, and three sanitizers scrub hotkey/wallet from AI/comment output — which is why this is an oversight, not by-design.\n \nExposure: REST → hotkey + 3 financial fields; MCP → 3 financial fields (hotkey redacted).\n \n### PoC\n \n1. Get any valid session/API/MCP token.\n2. Pick a target `login` that is a confirmed miner.\n3. `GET /v1/contributors/{target}/profile` → 200 with `gittensor.hotkey`, `alphaPerDay`, `taoPerDay`, `usdPerDay`.\n4. `GET /v1/contributors/{target}/decision-pack` (same token) → 403, proving the missing gate.\n5. MCP `gittensory_get_contributor_profile` with `{target}` → result includes the three `*PerDay` fields.\n### Impact\n \nAny token holder can enumerate other miners' daily TAO/alpha/USD revenue (plus hotkey via REST) without authorization. All miners with snapshot data are affected.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@jsonbored/gittensory-mcp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.1.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/JSONbored/gittensory/security/advisories/GHSA-382c-vx95-w3p5"
}, {
"type" : "WEB",
"url" : "https://github.com/JSONbored/gittensory/commit/811ef5fb9d748170011f8854d88c64627ad666a0"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/JSONbored/gittensory"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-284" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-09T13:44:51Z",
"nvd_published_at" : null
}
}