Tina is a headless content management system. Prior to version 2.2.2, @tinacms/graphql uses string-based path containment checks in FilesystemBridge. That blocks plain ../ traversal, but it does not resolve symlink or junction targets.
If a symlink/junction already exists under the allowed content root, a path like content/posts/pivot/owned.md is still considered "inside" the base even though the real filesystem target can be outside it. As a result, FilesystemBridge.get(), put(), delete(), and glob() can operate on files outside the intended root. This issue has been patched in version 2.2.2.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Ssw Tinacms\/Graphql
cpe:2.3:a:ssw:tinacms\/graphql:*:*:*:*:*:node.js:*:*
|
— |
<= 2.2.1
|
References 2
https://github.com/tinacms/tinacms/security/advisories/GHSA-g9c2-gf25-3x67
https://github.com/tinacms/tinacms/security/advisories/GHSA-g9c2-gf25-3x67
https://github.com/tinacms/tinacms/commit/f124eabaca10dac9a4d765c9e4135813c4830…
https://github.com/tinacms/tinacms/commit/f124eabaca10dac9a4d765c9e4135813c4830955