obsidian-tc tokens can access arbitrary configured vaults
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| The-40-Thieves | obsidian-tc | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| The-40-thieves | Obsidian-tc |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-84c9-qqpq-2pq5 | obsidian-tc tokens can access arbitrary configured vaults |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.309% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
The-40-thieves
The-40-thieves obsidian-tc |
|
| Vendors & Products |
The-40-thieves
The-40-thieves obsidian-tc |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, tool dispatch does not compare the caller-controlled input.vault value with the vault bound to the caller, the JSON Web Token (JWT) has no vault claim, and the folder access-control list is shared globally. Any valid token can therefore select another configured vault and read, write, or delete its contents through affected tools. Version 1.3.1 fixes the vulnerability by binding tokens and request context to a vault and rejecting mismatched input.vault values before scope checks. | |
| Title | obsidian-tc tokens can access arbitrary configured vaults | |
| Weaknesses | CWE-639 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|