neotoma
Affected
- introduced
0.13.0, fixed0.14.0(semver)
Fixed versions
0.14.0
Fix
- Fixed version
0.14.0npm install [email protected]
Advisory
Also known as: None
neotoma has tenant isolation gap in relationship query endpoints
Summary
The /list_relationships and /retrieve_graph_neighborhood endpoints call getAuthenticatedUserId (confirming a valid session exists) but do not pass the resolved user ID into the Supabase query as an .eq("user_id", userId) filter. As a result, queries return rows from all users rather than scoping to the authenticated caller's data.
Affected code
`/list_relationships` (src/actions.ts):
getAuthenticatedUserId but does not apply .eq("user_id", userId) to the relationships query.or() string interpolation for entity ID matching without input validation`/retrieve_graph_neighborhood` (src/actions.ts):
Affected versions
v0.13.0
Prerequisites
An unauthenticated caller is rejected at the auth middleware layer. The gap requires a second user account on the instance.
Impact
An authenticated user with a known cross-user entity ID can retrieve relationship edges and graph neighborhood data belonging to another user. No write capability is exposed.
Severity
Low under current conditions — no multi-tenant deployments exist. Escalates to Medium the moment two or more user accounts share an instance.
Remediation
.eq("user_id", userId) to all Supabase queries in both handlersisNeotomaEntityId before query construction.or() string interpolation with separate scoped .eq() callsFix tracked in #365 (list_relationships) and #366 (retrieve_graph_neighborhood). Gate gap tracked in #372.
Low Basis: The source's own band: LOW
0.13.0, fixed 0.14.0 (semver)0.14.0
0.14.0npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0