جزئیات آسیب‌پذیری

Tina is a headless content management system. Prior to @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1, isAuthorized accepts a request-controlled clientID and asks isUserAuthorized to validate the bearer token against that selected TinaCloud app instead of the self-hosted site's configured app. An attacker with any TinaCloud account can submit the attacker's own app ID and valid token to a victim endpoint, causing TinaCloudBackendAuthProvider or an affected media authorized callback to accept the attacker's verified status across the tenant boundary. The vulnerable logic is present in packages/@tinacms/auth/src/index.ts and packages/next-tinacms-azure/src/auth.ts. Successful exploitation permits media listing, reading, upload, or deletion and, when TinaCloudBackendAuthProvider is used, GraphQL read, create, update, and delete operations on the victim's content without a victim account or victim interaction. This vulnerability is fixed in @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1.

• https://github.com/tinacms/tinacms/pull/7168 x_refsource_MISC
• https://github.com/tinacms/tinacms/commit/0a927a4f8d228dd05ee7ca4be32899bc190e73af x_refsource_MISC
• https://github.com/tinacms/tinacms/releases/tag/@tinacms/auth@1.1.4 x_refsource_MISC
• https://github.com/tinacms/tinacms/releases/tag/next-tinacms-azure@15.0.1 x_refsource_MISC
• https://github.com/tinacms/tinacms/security/advisories/GHSA-g74q-6g2f-874x x_refsource_CONFIRM