Tamery (formerly Conar) 0.32.0 before 0.99.0 contains a broken authorization vulnerability in the cloud sync API connectionsResources.create handler that allows authenticated users to attach resources to other users' connections. Attackers owning one connection can include a victim's connectionId in a batch request to insert attacker-named resource rows listed by the victim's client.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · wannabespaceNVD modified 2026-10-30 14:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/wannabespace/tamery/issues/601 issue-tracking
- https://github.com/wannabespace/tamery/commit/400a9001a661e5ab2f87c51de25da1c4afa7ceed patch
- https://github.com/wannabespace/tamery/blob/v0.32.0/apps/api/orpc/routers/connections-resources/create.ts#L14-L32 technical-description
- https://hackmd.io/@hieuPenguinnn/conar-broken-ownership-cross-user-write third-party-advisory
- https://github.com/wannabespace/tamery product
- https://www.vulncheck.com/advisories/tamery-conar-0.32.0-before-0.99.0-broken-authorization-via-connectionsresources-create third-party-advisory