GHSA-43r2-c7g8-prc8: Infoleak
Impact Bridge tool results filtered only the items array against the read ACL and passed sibling fields through unfiltered: tasksfilter emitted groups whose counts reflected denied notes, makemdquery returned ...result siblings, and listtemplates enumerated Templater template paths and parsed user-function bodies with no read-whitelist gate. A caller could infer or read data from notes outside its read ACL.
Patches Fixed in 1.3.1. Upgrade to >= 1.3.1. All path-attributable fields are now scrubbed or fail-closed, and listtemplates is gated on the read whitelist.
Workarounds Disable the affected bridge tools (tasksfilter, makemdquery, listtemplates) via tool visibility.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/obsidian-tcto a version that resolves this vulnerability.Fixed in 1.3.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.3.1 - Configuration
Disable the affected bridge tools: tasks_filter, makemd_query, and list_templates.
Affected bridge tools tool visibility = disabled
Event History
Frequently Asked Questions
Who can exploit this issue?
A caller with low-privileged access to the affected Bridge tools can exploit it over the network without user interaction. The caller must be able to invoke the affected tools, but can infer or read note data that falls outside its configured read ACL.
Which functions expose information outside the read ACL?
The affected functions are tasks_filter, makemd_query, and list_templates. tasks_filter can expose group counts reflecting denied notes, makemd_query can return unfiltered result siblings, and list_templates can enumerate template paths and parsed user-function bodies.
Are deployments on the default affected version vulnerable?
The advisory identifies affected behavior through the fixed release and does not state a default configuration or default version. Versions 1.3.1 and later contain the fix.
What can be done if upgrading is not immediately possible?
Disable tasks_filter, makemd_query, and list_templates using tool visibility. This prevents access to the affected Bridge tools until an upgrade to version 1.3.1 or later can be completed.
How can I determine whether an instance is remediated?
Verify that obsidian-tc is running version 1.3.1 or later. In fixed versions, path-attributable fields are scrubbed or fail closed, and list_templates is gated by the read whitelist.